diff options
| author | Thomas Falcon <tlfalcon@linux.ibm.com> | 2019-08-27 11:10:04 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-09-21 07:17:05 +0200 |
| commit | 6cce2adae3e17e75109d9a1088f1b1bb69d778b1 (patch) | |
| tree | 894aadbfa77358d31485d4f1eda53cf7c475465f /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 080ca754f5dbc8cc65b69902a81c901708adaf53 (diff) | |
ibmvnic: Do not process reset during or after device removal
[ Upstream commit 36f1031c51a2538e5558fb44c6d6b88f98d3c0f2 ]
Currently, the ibmvnic driver will not schedule device resets
if the device is being removed, but does not check the device
state before the reset is actually processed. This leads to a race
where a reset is scheduled with a valid device state but is
processed after the driver has been removed, resulting in an oops.
Fix this by checking the device state before processing a queued
reset event.
Reported-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Tested-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Signed-off-by: Thomas Falcon <tlfalcon@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions