From: syzbot <syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com>
To: benh@kernel.crashing.org, davem@davemloft.net,
gregkh@linuxfoundation.org, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, netdev@vger.kernel.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org,
torvalds@linux-foundation.org
Subject: Re: BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
Date: Thu, 11 Apr 2019 05:14:00 -0700 [thread overview]
Message-ID: <000000000000109c700586401f48@google.com> (raw)
In-Reply-To: <000000000000b7fd51058370d0d9@google.com>
syzbot has bisected this bug to:
commit 726e41097920a73e4c7c33385dcc0debb1281e18
Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Tue Jul 10 00:29:10 2018 +0000
drivers: core: Remove glue dirs from sysfs earlier
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f69eaf200000
start commit: 771acc7e Bluetooth: btusb: request wake pin with NOAUTOEN
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17f69eaf200000
console output: https://syzkaller.appspot.com/x/log.txt?x=13f69eaf200000
kernel config: https://syzkaller.appspot.com/x/.config?x=4fb64439e07a1ec0
dashboard link: https://syzkaller.appspot.com/bug?extid=91fd909b6e62ebe06131
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11770a8f200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128c945b200000
Reported-by: syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com
Fixes: 726e41097920 ("drivers: core: Remove glue dirs from sysfs earlier")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-04-11 12:14 UTC|newest]
Thread overview: 37+ 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
2019-04-11 12:14 ` syzbot [this message]
2019-04-11 21:50 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2020-12-09 8:02 Dmitry Vyukov
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=000000000000109c700586401f48@google.com \
--to=syzbot+91fd909b6e62ebe06131@syzkaller.appspotmail.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--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=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/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