On Wed, May 20, 2020 at 2:04 PM Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: > > syzbot <syzbot+08003d278f04ed0944e0@xxxxxxxxxxxxxxxxxxxxxxxxx> writes: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit: fb57b1fa Add linux-next specific files for 20200519 > > git tree: linux-next > > console output: https://syzkaller.appspot.com/x/log.txt?x=17c9196e100000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=2522f758a3588c2d > > dashboard link: https://syzkaller.appspot.com/bug?extid=08003d278f04ed0944e0 > > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > > > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > > Reported-by: syzbot+08003d278f04ed0944e0@xxxxxxxxxxxxxxxxxxxxxxxxx > > > > ============================= > > [ BUG: Invalid wait context ] > > 5.7.0-rc6-next-20200519-syzkaller #0 Not tainted > > ----------------------------- > > swapper/1/0 is trying to lock: > > ffff8880ae737518 (&pool->lock){..-.}-{3:3}, at: spin_lock include/linux/spinlock.h:353 [inline] > > ffff8880ae737518 (&pool->lock){..-.}-{3:3}, at: __queue_work+0x2bf/0x1350 kernel/workqueue.c:1448 > > Can you please disable CONFIG_PROVE_RAW_LOCK_NESTING for now? > > From the help text: > > NOTE: > There are known nesting problems. So if you enable this option expect > lockdep splats until these problems have been fully addressed which is > work in progress. This config switch allows to identify and analyze > these problems. It will be removed and the check permanentely enabled > once the main issues have been fixed. Hi Thomas, Done: https://github.com/google/syzkaller/commit/4afdfa205b55633e7eb9db03a9d099d7aa324801 We can obsolete this then: #syz invalid
