From: syzbot <syzbot+22e87cdf94021b984aa6@syzkaller.appspotmail.com>
To: bfields@fieldses.org, boqun.feng@gmail.com, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
will@kernel.org
Subject: Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected (2)
Date: Wed, 09 Sep 2020 06:19:06 -0700 [thread overview]
Message-ID: <000000000000d7136005aee14bf9@google.com> (raw)
In-Reply-To: <0000000000002cdf7305aedd838d@google.com>
syzbot has bisected this issue to:
commit f08e3888574d490b31481eef6d84c61bedba7a47
Author: Boqun Feng <boqun.feng@gmail.com>
Date: Fri Aug 7 07:42:30 2020 +0000
lockdep: Fix recursive read lock related safe->unsafe detection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13034be1900000
start commit: dff9f829 Add linux-next specific files for 20200908
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10834be1900000
console output: https://syzkaller.appspot.com/x/log.txt?x=17034be1900000
kernel config: https://syzkaller.appspot.com/x/.config?x=37b3426c77bda44c
dashboard link: https://syzkaller.appspot.com/bug?extid=22e87cdf94021b984aa6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108b740d900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12daa9ed900000
Reported-by: syzbot+22e87cdf94021b984aa6@syzkaller.appspotmail.com
Fixes: f08e3888574d ("lockdep: Fix recursive read lock related safe->unsafe detection")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-09 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:48 WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected (2) syzbot
2020-09-09 13:19 ` syzbot [this message]
2020-09-10 7:15 ` Boqun Feng
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=000000000000d7136005aee14bf9@google.com \
--to=syzbot+22e87cdf94021b984aa6@syzkaller.appspotmail.com \
--cc=bfields@fieldses.org \
--cc=boqun.feng@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.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 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.