From: syzbot <syzbot+3025b9294f8cb0ede850@syzkaller.appspotmail.com>
To: anant.thazhemadam@gmail.com, bjorn.andersson@linaro.org,
colin.king@canonical.com, dan.carpenter@oracle.com,
davem@davemloft.net, dragonjetli@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, manivannan.sadhasivam@linaro.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: suspicious RCU usage in ctrl_cmd_new_lookup
Date: Thu, 22 Oct 2020 05:40:05 -0700 [thread overview]
Message-ID: <0000000000006f439b05b241c3c5@google.com> (raw)
In-Reply-To: <000000000000add83505a8e38c4c@google.com>
syzbot suspects this issue was fixed by commit:
commit a7809ff90ce6c48598d3c4ab54eb599bec1e9c42
Author: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Date: Sat Sep 26 16:56:25 2020 +0000
net: qrtr: ns: Protect radix_tree_deref_slot() using rcu read locks
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=143867c8500000
start commit: 7ae77150 Merge tag 'powerpc-5.8-1' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d195fe572fb15312
dashboard link: https://syzkaller.appspot.com/bug?extid=3025b9294f8cb0ede850
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11802cf9100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=144acc03100000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: qrtr: ns: Protect radix_tree_deref_slot() using rcu read locks
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-10-22 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 7:29 WARNING: suspicious RCU usage in ctrl_cmd_new_lookup syzbot
2020-07-02 9:44 ` syzbot
2020-10-22 12:40 ` syzbot [this message]
2020-11-11 11:49 ` 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=0000000000006f439b05b241c3c5@google.com \
--to=syzbot+3025b9294f8cb0ede850@syzkaller.appspotmail.com \
--cc=anant.thazhemadam@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=dragonjetli@gmail.com \
--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 \
/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).