diff options
author | Hannes Reinecke <hare@suse.de> | 2020-01-16 13:20:53 +0300 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2020-01-21 07:58:14 +0300 |
commit | 0e2209629fec427ba75a6351486153a9feddd36b (patch) | |
tree | 2d6e8431b0261408bbc70342aa4e74f8b69e0099 /drivers/target | |
parent | 28d76df18f0ad5bcf5fa48510b225f0ed262a99b (diff) | |
download | linux-0e2209629fec427ba75a6351486153a9feddd36b.tar.xz |
scsi: fnic: do not queue commands during fwreset
When a link is going down the driver will be calling fnic_cleanup_io(),
which will traverse all commands and calling 'done' for each found command.
While the traversal is handled under the host_lock, calling 'done' happens
after the host_lock is being dropped.
As fnic_queuecommand_lck() is being called with the host_lock held, it
might well be that it will pick the command being selected for abortion
from the above routine and enqueue it for sending, but then 'done' is being
called on that very command from the above routine.
Which of course confuses the hell out of the scsi midlayer.
So fix this by not queueing commands when fnic_cleanup_io is active.
Link: https://lore.kernel.org/r/20200116102053.62755-1-hare@suse.de
Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/target')
0 files changed, 0 insertions, 0 deletions