linux-kernel - Re: [syzbot] WARNING in io_wqe

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:   Tue, 8 Jun 2021 17:47:24 +0800
From:   Hao Xu <haoxu@...ux.alibaba.com>
To:     syzbot <syzbot+ea2f1484cffe5109dc10@...kaller.appspotmail.com>,
        asml.silence@...il.com, axboe@...nel.dk, io-uring@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: Re: [syzbot] WARNING in io_wqe_enqueue

在 2021/6/5 上午4:22, syzbot 写道:
> syzbot has bisected this issue to:
> 
> commit 24369c2e3bb06d8c4e71fd6ceaf4f8a01ae79b7c
> Author: Pavel Begunkov <asml.silence@...il.com>
> Date:   Tue Jan 28 00:15:48 2020 +0000
> 
>      io_uring: add io-wq workqueue sharing
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17934777d00000
> start commit:   f88cd3fb Merge tag 'vfio-v5.13-rc5' of git://github.com/aw..
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=14534777d00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10534777d00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=82d85e75046e5e64
> dashboard link: https://syzkaller.appspot.com/bug?extid=ea2f1484cffe5109dc10
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16d5772fd00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10525947d00000
> 
> Reported-by: syzbot+ea2f1484cffe5109dc10@...kaller.appspotmail.com
> Fixes: 24369c2e3bb0 ("io_uring: add io-wq workqueue sharing")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> 
This is not a bug, the repro program first set RLIMIT_NPROC to 0, then 
submits an unbound work whcih raises a warning of
WARN_ON_ONCE(!acct->max_workers). Since unbound->max_workers is
task_rlimit(current, RLIMIT_NPROC), so it is expected.