public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+79a4cc863a8db58cd92b@syzkaller.appspotmail.com>
To: axboe@kernel.dk, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] WARNING in io_wq_put_and_exit
Date: Tue, 14 Apr 2026 07:06:33 -0700	[thread overview]
Message-ID: <69de49e9.a00a0220.468cb.0061.GAE@google.com> (raw)
In-Reply-To: <69a41fc9.050a0220.3a55be.005a.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    d60bc1401583 Merge tag 'pwrseq-updates-for-v7.1-rc1' of gi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=168b7b02580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=36e12cb4499e2de4
dashboard link: https://syzkaller.appspot.com/bug?extid=79a4cc863a8db58cd92b
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=123f04ce580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e3bb6cfdd5a9/disk-d60bc140.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7d84405a4b00/vmlinux-d60bc140.xz
kernel image: https://storage.googleapis.com/syzbot-assets/de74b233e91c/bzImage-d60bc140.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+79a4cc863a8db58cd92b@syzkaller.appspotmail.com

RAX: ffffffffffffffda RBX: 00007f8d42c15fa0 RCX: 00007f8d4299c819
RDX: 0000000000000000 RSI: 0000200000000080 RDI: 0000000000000084
RBP: 00007f8d42a32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8d42c15fac R14: 00007f8d42c15fa0 R15: 00007f8d42c15fa0
 </TASK>
------------[ cut here ]------------
!test_bit(IO_WQ_BIT_EXIT, &wq->state)
WARNING: io_uring/io-wq.c:1396 at io_wq_put_and_exit+0x8a7/0x9d0 io_uring/io-wq.c:1396, CPU#0: syz.0.19/5987
Modules linked in:
CPU: 0 UID: 0 PID: 5987 Comm: syz.0.19 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
RIP: 0010:io_wq_put_and_exit+0x8a7/0x9d0 io_uring/io-wq.c:1396
Code: ff e8 7d bf 17 fd 44 0f b6 74 24 78 31 ff 44 89 f6 e8 bd b9 17 fd 45 84 f6 0f 85 1a fd ff ff e9 67 fd ff ff e8 5a bf 17 fd 90 <0f> 0b 90 e9 00 f8 ff ff e8 8c 5e 83 fd e9 72 f8 ff ff 48 8b 3c 24
RSP: 0018:ffffc900036d7b50 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88807a8fa000 RCX: ffffffff84f04326
RDX: ffff88801e390000 RSI: ffffffff84f04b26 RDI: ffff88801e390000
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 1ffff920006daf8c
R13: 0000000000000000 R14: ffff88801e390970 R15: ffff888032be0c18
FS:  00005555898aa500(0000) GS:ffff888124332000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000000c0 CR3: 0000000077c62000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 __io_uring_add_tctx_node+0x3e8/0x4c0 io_uring/tctx.c:174
 io_uring_create io_uring/io_uring.c:3063 [inline]
 io_uring_setup.cold+0x1993/0x1c7e io_uring/io_uring.c:3108
 __do_sys_io_uring_setup io_uring/io_uring.c:3142 [inline]
 __se_sys_io_uring_setup io_uring/io_uring.c:3133 [inline]
 __x64_sys_io_uring_setup+0xc2/0x170 io_uring/io_uring.c:3133
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x10b/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8d4299c819
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:00007ffe9e8909a8 EFLAGS: 00000246 ORIG_RAX: 00000000000001a9
RAX: ffffffffffffffda RBX: 00007f8d42c15fa0 RCX: 00007f8d4299c819
RDX: 0000000000000000 RSI: 0000200000000080 RDI: 0000000000000084
RBP: 00007f8d42a32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8d42c15fac R14: 00007f8d42c15fa0 R15: 00007f8d42c15fa0
 </TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

      reply	other threads:[~2026-04-14 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01 11:15 [syzbot] [io-uring?] WARNING in io_wq_put_and_exit syzbot
2026-04-14 14:06 ` syzbot [this message]

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=69de49e9.a00a0220.468cb.0061.GAE@google.com \
    --to=syzbot+79a4cc863a8db58cd92b@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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