diff options
author | Johannes Thumshirn <jthumshirn@suse.de> | 2016-04-05 09:50:44 (GMT) |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2016-04-15 20:51:53 (GMT) |
commit | f05795d3d771f30a7bdc3a138bf714b06d42aa95 (patch) | |
tree | c4cea319f50515a6fcb96114ef7e7653e699cc27 /drivers/rapidio/rio-sysfs.c | |
parent | be2a266d2a163a332666f396ea128a6bcc6882f7 (diff) | |
download | linux-f05795d3d771f30a7bdc3a138bf714b06d42aa95.tar.xz |
scsi: Add intermediate STARGET_REMOVE state to scsi_target_state
Add intermediate STARGET_REMOVE state to scsi_target_state to avoid
running into the BUG_ON() in scsi_target_reap(). The STARGET_REMOVE
state is only valid in the path from scsi_remove_target() to
scsi_target_destroy() indicating this target is going to be removed.
This re-fixes the problem introduced in commits bc3f02a795d3 ("[SCSI]
scsi_remove_target: fix softlockup regression on hot remove") and
40998193560d ("scsi: restart list search after unlock in
scsi_remove_target") in a more comprehensive way.
[mkp: Included James' fix for scsi_target_destroy()]
Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Fixes: 40998193560dab6c3ce8d25f4fa58a23e252ef38
Cc: stable@vger.kernel.org
Reported-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Tested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Reviewed-by: Ewan D. Milne <emilne@redhat.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Reviewed-by: James Bottomley <jejb@linux.vnet.ibm.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/rapidio/rio-sysfs.c')
0 files changed, 0 insertions, 0 deletions