summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/intel/ice/ice_base.c
diff options
context:
space:
mode:
authorMitch Williams <mitch.a.williams@intel.com>2019-12-12 03:13:05 -0800
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2020-01-03 16:08:33 -0800
commit1f45ebe0d8fbe6178670b663005f38ef8535db5d (patch)
tree35d10fb94a9e64f84d782bff09cd590cdb9f0d27 /drivers/net/ethernet/intel/ice/ice_base.c
parentac614b13fe71ec561b4a540c9f3ef095da5a7114 (diff)
downloadlinux-1f45ebe0d8fbe6178670b663005f38ef8535db5d.tar.bz2
ice: add extra check for null Rx descriptor
In the case where the hardware gives us a null Rx descriptor, it is theoretically possible that we could call one of our skb-construction functions with no data pointer, which would cause a panic. In real life, this will never happen - we only get null RX descriptors as the final descriptor in a chain of otherwise-valid descriptors. When this happens, the skb will be extant and we'll just call ice_add_rx_frag(), which can deal with empty data buffers. Unfortunately, Coverity does not have intimate knowledge of our hardware, so we must add a check here. Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'drivers/net/ethernet/intel/ice/ice_base.c')
0 files changed, 0 insertions, 0 deletions