On Wed, Jan 18, 2012 at 10:51 AM, Bart Van Assche <bvanassche@xxxxxxx> wrote: >> cf http://www.spinics.net/lists/linux-scsi/msg56254.html > With which SCSI low-level diver does that occur and how does the call > stack look like ? I haven't encountered any such issues while testing > the srp-ha patch set. However, I have to admit that the issues > mentioned in the description of commit 3308511 were discovered while > testing the srp-ha patch set. I assume you're asking about the crash on hot unplug... Anyway, I've seen it with mp2tsas, looking like [<ffffffff8130078b>] scsi_setup_blk_pc_cmnd+0x2b/0x170 [<ffffffff8130091d>] scsi_prep_fn+0x4d/0x60 [<ffffffff81227794>] blk_peek_request+0xb4/0x240 [<ffffffff813010cd>] scsi_request_fn+0x47d/0x4b0 [<ffffffff81223bff>] __blk_run_queue+0x1f/0x80 [<ffffffff8122b808>] blk_execute_rq_nowait+0x68/0xc0 in my case I think there is some SG_IO stuff in flight for SCSI reservations; the cdrom case I linked to also has scsi_setup_blk_pc_cmnd in the trace and mentions an ioctl for medium presence. So maybe regular block IO is OK now but not non-IO commands. - R. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
