summaryrefslogtreecommitdiff
path: root/Documentation/i2c
diff options
context:
space:
mode:
authorBo Chen <chenbo@pdx.edu>2018-07-23 09:01:29 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-10-10 08:52:09 +0200
commitc5bf8b49cc5a8416aea41645e64cdb8aa613c788 (patch)
treecd4155f4c61d29bb5eae7cd298aa1b09455c9c92 /Documentation/i2c
parentaa1c657ae2c320372fceeea98c0e6d25102f9d33 (diff)
e1000: check on netif_running() before calling e1000_up()
[ Upstream commit cf1acec008f8d7761aa3fd7c4bca7e17b2d2512d ] When the device is not up, the call to 'e1000_up()' from the error handling path of 'e1000_set_ringparam()' causes a kernel oops with a null-pointer dereference. The null-pointer dereference is triggered in function 'e1000_alloc_rx_buffers()' at line 'buffer_info = &rx_ring->buffer_info[i]'. This bug was reported by COD, a tool for testing kernel module binaries I am building. This bug was also detected by KFI from Dr. Kai Cong. This patch fixes the bug by checking on 'netif_running()' before calling 'e1000_up()' in 'e1000_set_ringparam()'. Signed-off-by: Bo Chen <chenbo@pdx.edu> Acked-by: Alexander Duyck <alexander.h.duyck@intel.com> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/i2c')
0 files changed, 0 insertions, 0 deletions