From: syzbot <syzbot+b48868c46e62c1c4cb2c@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, paolobertinetti200f4@proton.me,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] WARNING: suspicious RCU usage in mas_start (2)
Date: Mon, 21 Sep 2026 19:41:02 -0700 [thread overview]
Message-ID: <6ab1eabe.71f81b7d.15fa6d.003b.GAE@google.com> (raw)
In-Reply-To: <179001646572.88583.7894729070981725004@proton.me>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in io_wq_put_and_exit
------------[ cut here ]------------
time_after(jiffies, warn_timeout)
WARNING: io_uring/io-wq.c:1378 at io_wq_exit_workers io_uring/io-wq.c:1378 [inline], CPU#0: syz.0.29/6458
WARNING: io_uring/io-wq.c:1378 at io_wq_put_and_exit+0x736/0xaa0 io_uring/io-wq.c:1407, CPU#0: syz.0.29/6458
Modules linked in:
CPU: 0 UID: 0 PID: 6458 Comm: syz.0.29 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2026
RIP: 0010:io_wq_exit_workers io_uring/io-wq.c:1378 [inline]
RIP: 0010:io_wq_put_and_exit+0x736/0xaa0 io_uring/io-wq.c:1407
Code: 78 22 e8 5d 74 ee fc 4c 89 e7 4c 89 fe e8 a2 c4 0d 07 48 85 c0 75 18 e8 48 74 ee fc 80 3c 2b 00 75 bb eb c5 e8 3b 74 ee fc 90 <0f> 0b 90 eb d8 e8 30 74 ee fc 4c 8b 2c 24 4d 8d 7d 08 4c 89 fd 48
RSP: 0018:ffffc9000207f838 EFLAGS: 00010293
RAX: ffffffff84d967c5 RBX: 1ffffffff1d41e50 RCX: ffff88807d221f40
RDX: 0000000000000000 RSI: ffffffffffffe945 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffffff907a517f R09: 1ffffffff20f4a2f
R10: dffffc0000000000 R11: fffffbfff20f4a30 R12: ffff888028864018
R13: 0000000100003546 R14: 0000000100004c01 R15: 0000000000001b58
FS: 00007fd861d256c0(0000) GS:ffff888124ccb000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055944da2bd51 CR3: 000000002b20a000 CR4: 0000000000350ef0
Call Trace:
<TASK>
io_uring_clean_tctx+0x12e/0x1b0 io_uring/tctx.c:258
io_uring_cancel_generic+0x6c0/0x7d0 io_uring/cancel.c:655
io_uring_files_cancel include/linux/io_uring.h:20 [inline]
do_exit+0x39f/0x2360 kernel/exit.c:952
do_group_exit+0x22d/0x2f0 kernel/exit.c:1155
get_signal+0x121b/0x12c0 kernel/signal.c:3112
arch_do_signal_or_restart+0xbb/0x860 arch/x86/kernel/signal.c:337
__exit_to_user_mode_loop kernel/entry/common.c:66 [inline]
exit_to_user_mode_loop+0x10e/0x770 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:343 [inline]
do_syscall_64+0x328/0x520 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd860d9e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd861d250e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007fd861025fa8 RCX: 00007fd860d9e159
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fd861025fa8
RBP: 00007fd861025fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd861026038 R14: 00007fffbb02fd80 R15: 00007fffbb02fe68
</TASK>
Tested on:
commit: f0100363 Merge tag 'xfs-fixes-7.3-rc5' of gitolite.ker..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1147745e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9d4242cb1c54cdf7
dashboard link: https://syzkaller.appspot.com/bug?extid=b48868c46e62c1c4cb2c
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=114f3525580000
next parent reply other threads:[~2026-09-22 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <179001646572.88583.7894729070981725004@proton.me>
2026-09-22 2:41 ` syzbot [this message]
2026-09-14 21:26 syzbot
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=6ab1eabe.71f81b7d.15fa6d.003b.GAE@google.com \
--to=syzbot+b48868c46e62c1c4cb2c@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paolobertinetti200f4@proton.me \
--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
all inboxes | Powered by JetHome®