On 11/18/19 7:23 PM, Eric Biggers wrote: > Hi Jens, > > On Mon, Oct 28, 2019 at 03:00:08PM -0600, Jens Axboe wrote: >> This is fixed in my for-next branch for a few days at least, unfortunately >> linux-next is still on the old one. Next version should be better. > > This is still occurring on linux-next. Here's a report on next-20191115 from > https://syzkaller.appspot.com/text?tag=CrashReport&x=16fa3d1ce00000 Hmm, I'll take a look. Looking at the reproducer, it's got a massive sleep at the end. I take it this triggers before that time actually passes? Because that's around 11.5 days of sleep. No luck reproducing this so far, I'll try on linux-next. -- Jens Axboe
