Re: [PATCH-v2 00/14] iscsi-target: iSCSI target v4.1.0-rc1 series initial merge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 25, 2011 at 4:06 PM, James Bottomley
<James.Bottomley@xxxxxxx> wrote:
> Explain first what lock inversion problems you see ... those usually
> only happen if you have the in the kernel upcall thread waiting for
> completion.

In this context asynchronous upcalls have their problems too: the
in-kernel and the user space visible state may become inconsistent.
What will happen if processing of such notifications is delayed and
concurrently attempts are made from user space to act on these objects
? I'm afraid that could result in horrible race conditions.

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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux