From: syzbot <syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com>
To: davem@davemloft.net, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
Date: Wed, 10 Apr 2019 18:43:07 -0700 [thread overview]
Message-ID: <000000000000cf0d860586374ecb@google.com> (raw)
In-Reply-To: <000000000000b7fd51058370d0d9@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 771acc7e Bluetooth: btusb: request wake pin with NOAUTOEN
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15f58add200000
kernel config: https://syzkaller.appspot.com/x/.config?x=4fb64439e07a1ec0
dashboard link: https://syzkaller.appspot.com/bug?extid=91fd909b6e62ebe06131
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11770a8f200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128c945b200000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
turning off the locking correctness validator.
CPU: 0 PID: 1174 Comm: kworker/u5:0 Not tainted 5.1.0-rc4+ #63
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: hci1 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:2591 [inline]
lookup_chain_cache_add kernel/locking/lockdep.c:2665 [inline]
validate_chain kernel/locking/lockdep.c:2685 [inline]
__lock_acquire.cold+0x250/0x50d kernel/locking/lockdep.c:3701
lock_acquire+0x16f/0x3f0 kernel/locking/lockdep.c:4211
__mutex_lock_common kernel/locking/mutex.c:925 [inline]
__mutex_lock+0xf7/0x1310 kernel/locking/mutex.c:1072
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1087
hci_dev_do_close+0x317/0xf20 net/bluetooth/hci_core.c:1696
hci_power_on+0x1d2/0x580 net/bluetooth/hci_core.c:2191
process_one_work+0x98e/0x1790 kernel/workqueue.c:2269
worker_thread+0x98/0xe40 kernel/workqueue.c:2415
kthread+0x357/0x430 kernel/kthread.c:253
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
next prev parent reply other threads:[~2019-04-11 1:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 18:04 BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! syzbot
2019-04-11 1:43 ` syzbot [this message]
2019-04-11 12:14 ` syzbot
2019-04-11 21:50 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2020-12-09 8:02 Dmitry Vyukov
2021-03-02 10:27 Johannes Thumshirn
2021-03-04 13:52 ` David Sterba
2022-07-26 12:32 Mikhail Gavrilov
2022-07-26 16:42 ` David Sterba
2022-07-26 19:19 ` Chris Murphy
2022-07-26 19:21 ` Chris Murphy
2022-07-26 20:42 ` David Sterba
2022-08-03 19:28 ` Mikhail Gavrilov
2022-08-03 20:00 ` Chris Murphy
2022-08-04 7:35 ` Mikhail Gavrilov
2022-08-04 11:23 ` Tetsuo Handa
2023-01-24 20:27 ` Mikhail Gavrilov
2023-01-25 17:15 ` David Sterba
2023-01-26 9:47 ` Mikhail Gavrilov
2023-01-26 17:38 ` Boqun Feng
2023-01-26 18:30 ` Waiman Long
2023-01-26 18:59 ` Boqun Feng
2023-01-26 19:07 ` Waiman Long
2023-01-26 22:42 ` Mikhail Gavrilov
2023-01-26 22:51 ` Boqun Feng
2023-01-26 23:49 ` Boqun Feng
2023-01-27 0:20 ` Waiman Long
2023-01-27 3:37 ` Chris Murphy
2023-01-27 4:07 ` Boqun Feng
2023-01-27 5:35 ` Mikhail Gavrilov
2023-01-27 14:26 ` Waiman Long
2023-01-27 15:33 ` Chris Murphy
2025-03-09 22:51 ` Mikhail Gavrilov
2025-03-10 11:23 ` Peter Zijlstra
2025-03-10 9:08 ` Peter Zijlstra
2025-03-10 13:01 ` Peter Zijlstra
2025-03-10 11:21 ` Peter Zijlstra
2025-03-10 16:37 ` Boqun Feng
2025-09-23 7:03 ` Mikhail Gavrilov
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=000000000000cf0d860586374ecb@google.com \
--to=syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--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 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.