On 1/17/20 3:05 PM, Pavel Begunkov wrote: > I'm hitting a bug with yesterday's for-next (e.g. 126c20adbd98f2eff00c837afc). > I'll debug it in several days, if nobody would do it by then. > > kernel: yesterday's for-next (e.g. 126c20adbd98f2eff00c837afc) > How to reproduce: run ./file-update in a loop (for me 10th run hit the problem) Let me know if it still happens in the current tree, I fixed the wait on this. But it might be something new, we'll see. -- Jens Axboe
