From: syzbot <syzbot+aaa6fa4949cc5d9b7b25@syzkaller.appspotmail.com>
To: dvyukov@google.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
will.deacon@arm.com
Subject: Re: BUG: MAX_LOCKDEP_CHAINS too low!
Date: Sun, 20 Oct 2019 16:33:11 -0700 [thread overview]
Message-ID: <0000000000008a279405955ffd35@google.com> (raw)
In-Reply-To: <0000000000007523a60576e80a47@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 4fe34d61 Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1176cd40e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e0ac4d9b35046343
dashboard link: https://syzkaller.appspot.com/bug?extid=aaa6fa4949cc5d9b7b25
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14150b40e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e122ff600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+aaa6fa4949cc5d9b7b25@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 11772 Comm: kworker/u5:486 Not tainted 5.4.0-rc3+ #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: hci1600 hci_power_on
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
add_chain_cache kernel/locking/lockdep.c:2816 [inline]
lookup_chain_cache_add kernel/locking/lockdep.c:2915 [inline]
validate_chain kernel/locking/lockdep.c:2936 [inline]
__lock_acquire.cold+0x325/0x385 kernel/locking/lockdep.c:3955
lock_acquire+0x190/0x410 kernel/locking/lockdep.c:4487
process_one_work+0x91c/0x1740 kernel/workqueue.c:2245
worker_thread+0x98/0xe40 kernel/workqueue.c:2415
kthread+0x361/0x430 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
next prev parent reply other threads:[~2019-10-20 23:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 5:51 BUG: MAX_LOCKDEP_CHAINS too low! syzbot
2018-09-28 6:06 ` Dmitry Vyukov
2018-09-28 7:00 ` Peter Zijlstra
2018-09-28 7:56 ` Dmitry Vyukov
2020-01-09 10:59 ` Dmitry Vyukov
2020-01-13 11:11 ` Dmitry Vyukov
2020-01-15 21:53 ` Cong Wang
2020-01-16 5:25 ` Dmitry Vyukov
2020-01-16 15:32 ` Taehee Yoo
2020-01-16 17:05 ` Dmitry Vyukov
2020-01-16 15:09 ` Taehee Yoo
2020-01-18 20:41 ` Cong Wang
2020-03-04 8:03 ` Dmitry Vyukov
2020-03-04 23:19 ` Cong Wang
2020-01-14 8:43 ` Peter Zijlstra
2020-01-14 10:18 ` Dmitry Vyukov
2019-10-20 23:33 ` syzbot [this message]
2020-04-15 18:52 ` Cong Wang
2020-04-15 19:17 ` syzbot
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=0000000000008a279405955ffd35@google.com \
--to=syzbot+aaa6fa4949cc5d9b7b25@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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