From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: 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: Fri, 12 Apr 2019 07:50:20 +1000 [thread overview]
Message-ID: <068bf2f6512c10fd4ca71ea6017e27fa5928d166.camel@kernel.crashing.org> (raw)
In-Reply-To: <000000000000109c700586401f48@google.com>
On Thu, 2019-04-11 at 05:14 -0700, syzbot wrote:
> 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
Greg, any idea what this is ? The log isn't terribly readable. The
above patch fixes a real bug that causes use after free and memory
corruption under some circumstances. I wonder if the BT stack is itself
manipulating stale objects ?
Ben.
> 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
prev parent reply other threads:[~2019-04-11 21:50 UTC|newest]
Thread overview: 4+ 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
2019-04-11 21:50 ` Benjamin Herrenschmidt [this message]
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=068bf2f6512c10fd4ca71ea6017e27fa5928d166.camel@kernel.crashing.org \
--to=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;
as well as URLs for NNTP newsgroup(s).