From: syzbot <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: Re: [syzbot] WARNING in io_wq_submit_work (2)
Date: Sat, 11 Sep 2021 06:53:29 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
syzbot has found a reproducer for the following issue on:
HEAD commit: 926de8c4326c Merge tag 'acpi-5.15-rc1-3' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17fefe8b300000
kernel config: https://syzkaller.appspot.com/x/.config?x=37df9ef5660a8387
dashboard link: https://syzkaller.appspot.com/bug?extid=bc2d90f602545761f287
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e4357d300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1173a663300000
The issue was bisected to:
commit 3146cba99aa284b1d4a10fbd923df953f1d18035
Author: Jens Axboe <[email protected]>
Date: Wed Sep 1 17:20:10 2021 +0000
io-wq: make worker creation resilient against signals
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11098e0d300000
final oops: https://syzkaller.appspot.com/x/report.txt?x=13098e0d300000
console output: https://syzkaller.appspot.com/x/log.txt?x=15098e0d300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]
Fixes: 3146cba99aa2 ("io-wq: make worker creation resilient against signals")
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 000000000043f6d9
RDX: 0000000000000000 RSI: 0000000000000304 RDI: 0000000000000003
RBP: 00007ffed8512ba0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000000 R14: 00000000004ad018 R15: 0000000000400488
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6524 at fs/io_uring.c:1164 req_ref_get fs/io_uring.c:1164 [inline]
WARNING: CPU: 0 PID: 6524 at fs/io_uring.c:1164 io_wq_submit_work+0x272/0x300 fs/io_uring.c:6733
Modules linked in:
CPU: 0 PID: 6524 Comm: syz-executor339 Not tainted 5.14.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:req_ref_get fs/io_uring.c:1164 [inline]
RIP: 0010:io_wq_submit_work+0x272/0x300 fs/io_uring.c:6733
Code: e8 43 33 91 ff 83 fb 7f 76 1b e8 f9 2b 91 ff be 04 00 00 00 4c 89 ef e8 3c 7a d8 ff f0 ff 45 a4 e9 41 fe ff ff e8 de 2b 91 ff <0f> 0b eb dc e8 d5 2b 91 ff 4c 89 e7 e8 ed db fb ff 48 85 c0 49 89
RSP: 0018:ffffc9000116fae8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 000000000000007f RCX: 0000000000000000
RDX: ffff88801be91c80 RSI: ffffffff81e4e162 RDI: 0000000000000003
RBP: ffff88801a793978 R08: 000000000000007f R09: ffff88801a79391f
R10: ffffffff81e4e13d R11: 0000000000000000 R12: ffff88801a7938c0
R13: ffff88801a79391c R14: ffff88801a793918 R15: 0000000000100000
FS: 0000000000a12300(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000480310 CR3: 00000000778f6000 CR4: 0000000000350ef0
Call Trace:
io_run_cancel fs/io-wq.c:809 [inline]
io_acct_cancel_pending_work.isra.0+0x2a9/0x5e0 fs/io-wq.c:950
io_wqe_cancel_pending_work+0x6c/0x130 fs/io-wq.c:968
io_wq_destroy fs/io-wq.c:1185 [inline]
io_wq_put_and_exit+0x7d1/0xc70 fs/io-wq.c:1198
io_uring_clean_tctx fs/io_uring.c:9609 [inline]
io_uring_cancel_generic+0x5fe/0x740 fs/io_uring.c:9689
io_uring_files_cancel include/linux/io_uring.h:16 [inline]
do_exit+0x265/0x2a30 kernel/exit.c:780
do_group_exit+0x125/0x310 kernel/exit.c:922
__do_sys_exit_group kernel/exit.c:933 [inline]
__se_sys_exit_group kernel/exit.c:931 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:931
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x43e3d9
Code: 90 49 c7 c0 c0 ff ff ff be e7 00 00 00 ba 3c 00 00 00 eb 12 0f 1f 44 00 00 89 d0 0f 05 48 3d 00 f0 ff ff 77 1c f4 89 f0 0f 05 <48> 3d 00 f0 ff ff 76 e7 f7 d8 64 41 89 00 eb df 0f 1f 80 00 00 00
RSP: 002b:00007ffed8512b78 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00000000004af3b0 RCX: 000000000043e3d9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000004af3b0
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
next prev parent reply other threads:[~2021-09-11 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 0:09 [syzbot] WARNING in io_wq_submit_work (2) syzbot
2021-09-09 0:18 ` Pavel Begunkov
2021-09-09 0:56 ` syzbot
2021-09-11 13:53 ` syzbot [this message]
2021-10-11 20:32 ` syzbot
2021-10-12 10:42 ` Pavel Begunkov
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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