From: syzbot <syzbot+3eec59e770685e3dc879@syzkaller.appspotmail.com>
To: bjorn.andersson@linaro.org, davem@davemloft.net,
ebiggers@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, manivannan.sadhasivam@linaro.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: BUG: using smp_processor_id() in preemptible code in radix_tree_node_alloc
Date: Thu, 04 Jun 2020 23:09:03 -0700 [thread overview]
Message-ID: <0000000000001ac18b05a75019ab@google.com> (raw)
In-Reply-To: <000000000000a363b205a74ca6a2@google.com>
syzbot has bisected this bug to:
commit e42671084361302141a09284fde9bbc14fdd16bf
Author: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Date: Thu May 7 12:53:06 2020 +0000
net: qrtr: Do not depend on ARCH_QCOM
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e22212100000
start commit: acf25aa6 Merge tag 'Smack-for-5.8' of git://github.com/csc..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14122212100000
console output: https://syzkaller.appspot.com/x/log.txt?x=10122212100000
kernel config: https://syzkaller.appspot.com/x/.config?x=5263d9b5bce03c67
dashboard link: https://syzkaller.appspot.com/bug?extid=3eec59e770685e3dc879
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd4c1e100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1520c9de100000
Reported-by: syzbot+3eec59e770685e3dc879@syzkaller.appspotmail.com
Fixes: e42671084361 ("net: qrtr: Do not depend on ARCH_QCOM")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-06-05 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 2:02 BUG: using smp_processor_id() in preemptible code in radix_tree_node_alloc syzbot
2020-06-05 3:55 ` Eric Biggers
2020-06-05 11:29 ` Matthew Wilcox
2020-06-05 16:11 ` Eric Biggers
2020-06-05 6:09 ` syzbot [this message]
2021-06-07 16:47 ` [syzbot] " syzbot
2021-06-07 16:58 ` Matthew Wilcox
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=0000000000001ac18b05a75019ab@google.com \
--to=syzbot+3eec59e770685e3dc879@syzkaller.appspotmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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).