Re: [PATCH 1/1] bcache: use llist_for_each_entry_safe() in __closure_wake_up()

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

 



On 09/27/2017 10:48 PM, Michael Lyle wrote:
> Jens--
> 
> I think it's a race condition-- the individual closures remain valid.
> It's just that the list element has different meanings-- it's either a
> list actively being used to wake, or a linkage on one of several lists
> that is being used to await wake.  If a closure goes back to wait very
> quickly after being woken, it can end up connecting its new wait-list
> with the being-woken list.

Reading it a second time, looks like you are right. OK, then let's just
queue it up as-is, I'll add the Fixes line this time.

-- 
Jens Axboe




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux