diff options
author | Aleksandr Mishin <amishin@t-argos.ru> | 2024-06-05 13:11:35 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2024-06-07 16:22:19 +0300 |
commit | c44711b78608c98a3e6b49ce91678cd0917d5349 (patch) | |
tree | 94d4dbfccfb3f1ccbe1f488672b97071ceef0230 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | dbfb8864650ec0b69e0a1b9b667bf79c25ca33ca (diff) | |
download | linux-c44711b78608c98a3e6b49ce91678cd0917d5349.tar.xz |
liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet
In lio_vf_rep_copy_packet() pg_info->page is compared to a NULL value,
but then it is unconditionally passed to skb_add_rx_frag() which looks
strange and could lead to null pointer dereference.
lio_vf_rep_copy_packet() call trace looks like:
octeon_droq_process_packets
octeon_droq_fast_process_packets
octeon_droq_dispatch_pkt
octeon_create_recv_info
...search in the dispatch_list...
->disp_fn(rdisp->rinfo, ...)
lio_vf_rep_pkt_recv(struct octeon_recv_info *recv_info, ...)
In this path there is no code which sets pg_info->page to NULL.
So this check looks unneeded and doesn't solve potential problem.
But I guess the author had reason to add a check and I have no such card
and can't do real test.
In addition, the code in the function liquidio_push_packet() in
liquidio/lio_core.c does exactly the same.
Based on this, I consider the most acceptable compromise solution to
adjust this issue by moving skb_add_rx_frag() into conditional scope.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Fixes: 1f233f327913 ("liquidio: switchdev support for LiquidIO NIC")
Signed-off-by: Aleksandr Mishin <amishin@t-argos.ru>
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions