From: syzbot <syzbot+53f8ce8bbc07924b6417@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, peterz@infradead.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
will@kernel.org
Subject: Re: BUG: using __this_cpu_read() in preemptible code in trace_hardirqs_on
Date: Fri, 16 Oct 2020 13:33:05 -0700 [thread overview]
Message-ID: <000000000000f9990805b1cfab64@google.com> (raw)
In-Reply-To: <000000000000e921b305b18ba0a7@google.com>
syzbot has bisected this issue to:
commit 4d004099a668c41522242aa146a38cc4eb59cb1e
Author: Peter Zijlstra <peterz@infradead.org>
Date: Fri Oct 2 09:04:21 2020 +0000
lockdep: Fix lockdep recursion
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=174a766f900000
start commit: 9ff9b0d3 Merge tag 'net-next-5.10' of git://git.kernel.org..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14ca766f900000
console output: https://syzkaller.appspot.com/x/log.txt?x=10ca766f900000
kernel config: https://syzkaller.appspot.com/x/.config?x=d13c3fa80bc4bcc1
dashboard link: https://syzkaller.appspot.com/bug?extid=53f8ce8bbc07924b6417
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b63310500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1565657f900000
Reported-by: syzbot+53f8ce8bbc07924b6417@syzkaller.appspotmail.com
Fixes: 4d004099a668 ("lockdep: Fix lockdep recursion")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-10-16 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000e921b305b18ba0a7@google.com>
2020-10-16 17:16 ` BUG: using __this_cpu_read() in preemptible code in trace_hardirqs_on syzbot
2020-10-16 20:33 ` syzbot [this message]
2020-10-21 13:09 ` Dmitry Vyukov
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=000000000000f9990805b1cfab64@google.com \
--to=syzbot+53f8ce8bbc07924b6417@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--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 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).