From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+08003d278f04ed0944e0@syzkaller.appspotmail.com>,
fweisbec@gmail.com, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, mingo@kernel.org,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: Re: linux-next boot error: BUG: Invalid wait context ]
Date: Wed, 20 May 2020 14:04:22 +0200 [thread overview]
Message-ID: <877dx66ce1.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <000000000000598a2905a60d50cd@google.com>
syzbot <syzbot+08003d278f04ed0944e0@syzkaller.appspotmail.com> 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@syzkaller.appspotmail.com
>
> =============================
> [ 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.
Thanks,
tglx
next prev parent reply other threads:[~2020-05-20 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 5:03 linux-next boot error: BUG: Invalid wait context ] syzbot
2020-05-20 12:04 ` Thomas Gleixner [this message]
2020-05-20 13:41 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dx66ce1.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+08003d278f04ed0944e0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).