Hi Andrew!
After applying the patch the same lock exists:
#001: [ffff81006edc4080] {scsi_host_alloc}
.. held by: scsi_wq_4: 4255 [ffff81007edaf770, 110]
... acquired at: scsi_scan_target+0x51/0x87 [scsi_mod]
Thanks,
Maxim.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- problems with scsi_transport_fc and qla2xxx
- From: Maxim Kozover <[email protected]>
- Re: problems with scsi_transport_fc and qla2xxx
- From: Maxim Kozover <[email protected]>
- Re: problems with scsi_transport_fc and qla2xxx
- From: Andrew Morton <[email protected]>
- Re: problems with scsi_transport_fc and qla2xxx
- From: Stefan Kaltenbrunner <[email protected]>
- Re: problems with scsi_transport_fc and qla2xxx
- From: Andrew Vasquez <[email protected]>
- Re:Re: problems with scsi_transport_fc and qla2xxx
- From: Maxim Kozover <[email protected]>
- Re: Re: problems with scsi_transport_fc and qla2xxx
- From: "Mike Snitzer" <[email protected]>
- Re: Re: problems with scsi_transport_fc and qla2xxx
- From: Maxim Kozover <[email protected]>
- Re: problems with scsi_transport_fc and qla2xxx
- From: Andrew Vasquez <[email protected]>
- problems with scsi_transport_fc and qla2xxx
- Prev by Date: Re: Slab corruption in 2.6.16-rc5-mm2
- Next by Date: Re: [OT] inotify hack for locate
- Previous by thread: Re: Re: problems with scsi_transport_fc and qla2xxx
- Next by thread: Re[8]: problems with scsi_transport_fc and qla2xxx
- Index(es):
 |