From: syzbot <syzbot+8a249628ae32ea7de3a2@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andrii@kernel.org, andy@greyhouse.net,
ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, glider@google.com, hawk@kernel.org,
j.vosburgh@gmail.com, john.fastabend@gmail.com,
john.ogness@linutronix.de, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pmladek@suse.com, rdunlap@infradead.org,
songliubraving@fb.com, swboyd@chromium.org,
syzkaller-bugs@googlegroups.com, vfalico@gmail.com, yhs@fb.com
Subject: Re: [syzbot] BUG: MAX_LOCKDEP_CHAINS too low! (3)
Date: Sat, 11 Dec 2021 14:04:21 -0800 [thread overview]
Message-ID: <000000000000981d5005d2e60598@google.com> (raw)
In-Reply-To: <00000000000069e12f05d0b78c2d@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 6f513529296f Merge tag 'for-5.16-rc4-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10a8954db00000
kernel config: https://syzkaller.appspot.com/x/.config?x=221ffc09e39ebbd1
dashboard link: https://syzkaller.appspot.com/bug?extid=8a249628ae32ea7de3a2
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12777551b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a99a05b00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8a249628ae32ea7de3a2@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 6709 Comm: kworker/u4:7 Not tainted 5.16.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bond1948 bond_netdev_notify_work
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
add_chain_cache kernel/locking/lockdep.c:3649 [inline]
lookup_chain_cache_add kernel/locking/lockdep.c:3748 [inline]
validate_chain kernel/locking/lockdep.c:3769 [inline]
__lock_acquire.cold+0x372/0x3ab kernel/locking/lockdep.c:5027
lock_acquire kernel/locking/lockdep.c:5637 [inline]
lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602
process_one_work+0x921/0x1690 kernel/workqueue.c:2274
worker_thread+0x658/0x11f0 kernel/workqueue.c:2445
kthread+0x405/0x4f0 kernel/kthread.c:327
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
next prev parent reply other threads:[~2021-12-11 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 3:47 [syzbot] BUG: MAX_LOCKDEP_CHAINS too low! (3) syzbot
2021-12-11 22:04 ` syzbot [this message]
2024-03-06 1:01 ` [syzbot] " 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=000000000000981d5005d2e60598@google.com \
--to=syzbot+8a249628ae32ea7de3a2@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=andy@greyhouse.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=glider@google.com \
--cc=hawk@kernel.org \
--cc=j.vosburgh@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=songliubraving@fb.com \
--cc=swboyd@chromium.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vfalico@gmail.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.