From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+3eec59e770685e3dc879@syzkaller.appspotmail.com>
Cc: bjorn.andersson@linaro.org, brookebasile@gmail.com,
coreteam@netfilter.org, davem@davemloft.net, dsahern@kernel.org,
ducheng2@gmail.com, ebiggers@kernel.org, fw@strlen.de,
gregkh@linuxfoundation.org, kadlec@netfilter.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
manivannan.sadhasivam@linaro.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com,
yoshfuji@linux-ipv6.org
Subject: Re: [syzbot] BUG: using smp_processor_id() in preemptible code in radix_tree_node_alloc
Date: Mon, 7 Jun 2021 17:58:40 +0100 [thread overview]
Message-ID: <YL5QQE2GnJFWI4rB@casper.infradead.org> (raw)
In-Reply-To: <000000000000b9c68205c42fcacb@google.com>
On Mon, Jun 07, 2021 at 09:47:07AM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 43016d02cf6e46edfc4696452251d34bba0c0435
> Author: Florian Westphal <fw@strlen.de>
> Date: Mon May 3 11:51:15 2021 +0000
>
> netfilter: arptables: use pernet ops struct during unregister
Same wrong bisection.
#syz fix: qrtr: Convert qrtr_ports from IDR to XArray
prev parent reply other threads:[~2021-06-07 16:59 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
2021-06-07 16:47 ` [syzbot] " syzbot
2021-06-07 16:58 ` Matthew Wilcox [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=YL5QQE2GnJFWI4rB@casper.infradead.org \
--to=willy@infradead.org \
--cc=bjorn.andersson@linaro.org \
--cc=brookebasile@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ducheng2@gmail.com \
--cc=ebiggers@kernel.org \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+3eec59e770685e3dc879@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.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).