linux-kernel - Re: WARNING: suspicious RCU usage in io_init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 16 Oct 2020 09:05:05 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Qian Cai <cai@....pw>
Cc:     io-uring@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        viro@...iv.linux.org.uk,
        syzbot <syzbot+4596e1fcf98efa7d1745@...kaller.appspotmail.com>
Subject: Re: WARNING: suspicious RCU usage in io_init_identity

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@...kaller.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