On 08/29/12 05:12, Dan Williams wrote: > John reports: > BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u:8:2202] > [..] > Call Trace: > [<ffffffff8141782a>] scsi_remove_target+0xda/0x1f0 > [<ffffffff81421de5>] sas_rphy_remove+0x55/0x60 > [<ffffffff81421e01>] sas_rphy_delete+0x11/0x20 > [<ffffffff81421e35>] sas_port_delete+0x25/0x160 > [<ffffffff814549a3>] mptsas_del_end_device+0x183/0x270 > > ...introduced by commit 3b661a9 "[SCSI] fix hot unplug vs async scan race". Including that call stack in the patch description may create the misleading impression that this only occurs with the mptsas driver. This lockup also happens with at least the iSCSI initiator. See also http://lkml.org/lkml/2012/8/24/340. By the way, in order to get a patch in the stable tree the proper "Cc:" tag should be added in the patch description but the stable@xxxxxxxxxxxxxxx e-mail address should be left out from the Cc-list of the e-mail with the patch. Bart. -- 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
