From: Jens Axboe <axboe@kernel.dk>
To: Qian Cai <cai@lca.pw>
Cc: io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk,
syzbot <syzbot+4596e1fcf98efa7d1745@syzkaller.appspotmail.com>
Subject: Re: WARNING: suspicious RCU usage in io_init_identity
Date: Fri, 16 Oct 2020 09:05:05 -0600 [thread overview]
Message-ID: <1039be9b-ddb9-4f76-fda3-55d10f0bd286@kernel.dk> (raw)
In-Reply-To: <a7cac632aa89ed30c5c6deb9c67f428810aed9cb.camel@lca.pw>
On 10/16/20 9:02 AM, Qian Cai wrote:
> On Fri, 2020-10-16 at 01:12 -0700, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: b2926c10 Add linux-next specific files for 20201016
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=12fc877f900000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=6160209582f55fb1
>> dashboard link: https://syzkaller.appspot.com/bug?extid=4596e1fcf98efa7d1745
>> compiler: gcc (GCC) 10.1.0-syz 20200507
>>
>> Unfortunately, I don't have any reproducer for this issue yet.
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+4596e1fcf98efa7d1745@syzkaller.appspotmail.com
>>
>> =============================
>> WARNING: suspicious RCU usage
>> 5.9.0-next-20201016-syzkaller #0 Not tainted
>> -----------------------------
>> include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage!
>
> Introduced by the linux-next commits:
>
> 07950f53f85b ("io_uring: COW io_identity on mismatch")
>
> Can't find the patchset was posted anywhere. Anyway, this should fix it?
It's just in testing... I already folded in this change.
--
Jens Axboe
next prev parent reply other threads:[~2020-10-16 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 8:12 WARNING: suspicious RCU usage in io_init_identity syzbot
2020-10-16 15:02 ` Qian Cai
2020-10-16 15:05 ` Jens Axboe [this message]
2020-10-21 10:02 ` 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=1039be9b-ddb9-4f76-fda3-55d10f0bd286@kernel.dk \
--to=axboe@kernel.dk \
--cc=cai@lca.pw \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+4596e1fcf98efa7d1745@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).