James Smart wrote: > >> Actually, maybe, I should not have brought this up as it could just be >> more of a workaround of the core problem. For FC in fc_user_scan() do >> you need some sort of lock around the rport loop? > > Yes, I had noticed this as well. However, I don't think this is influencing > the deadlock. > iscsi needed a lock too. And so we ended up just adding a semaphore around the addition and deletion and scanning of sessions. We also do some weird things in that we initiate some tasks from userspace (scanning and shutting down devices, transport shutdown, etc), but the locking issues are similar and by doing some of the things in userspace iscsi is just trying to work around some of the issues. I was just thinking maybe your original thought about a more invasive locking change may be needed instead of the workaround I was suggesting earlier in the thread. - : 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
