On 2019/01/20 4:03, Dmitry Vyukov wrote: > On Sun, Apr 29, 2018 at 7:03 PM syzbot > <syzbot+cfa5d826b19395f19...@syzkaller.appspotmail.com> wrote: >> >> Hello, >> >> syzbot hit the following crash on upstream commit >> bf8f5de17442bba5f811e7e724980730e079ee11 (Sat Apr 28 17:05:04 2018 +0000) >> MAINTAINERS: add myself as maintainer of AFFS >> syzbot dashboard link: >> https://syzkaller.appspot.com/bug?extid=cfa5d826b19395f1940e >> >> Unfortunately, I don't have any reproducer for this crash yet. >> Raw console output: >> https://syzkaller.appspot.com/x/log.txt?id=5087555854794752 >> Kernel config: >> https://syzkaller.appspot.com/x/.config?id=7043958930931867332 >> compiler: gcc (GCC) 8.0.1 20180413 (experimental) > > This mentions __getblk_gfp. Is it the same as "INFO: task hung in > generic_file_write_iter": > https://syzkaller.appspot.com/bug?id=b3c7e1440aa8ece16bf557dbac427fdff1dad9d6 > and fixed with "blockdev: Fix livelocks on loop device"?
Yes, I think so. #syz dup: INFO: task hung in generic_file_write_iter
