linux-kernel - [syzbot] [io-uring?] WARNING in io_ring_exit

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>] [day] [month] [year] [list]

Message-ID: <0000000000008441e70611f52901@google.com>
Date: Thu, 22 Feb 2024 01:35:21 -0800
From: syzbot <syzbot+557a278955ff3a4d3938@...kaller.appspotmail.com>
To: asml.silence@...il.com, axboe@...nel.dk, io-uring@...r.kernel.org, 
	linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [io-uring?] WARNING in io_ring_exit_work (2)

Hello,

syzbot found the following issue on:

HEAD commit:    2c3b09aac00d Add linux-next specific files for 20240214
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14ba5b8a180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=176d2dcbf8ba7017
dashboard link: https://syzkaller.appspot.com/bug?extid=557a278955ff3a4d3938
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ac51042b61c6/disk-2c3b09aa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/012344301c35/vmlinux-2c3b09aa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cba3c3e5cd7c/bzImage-2c3b09aa.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+557a278955ff3a4d3938@...kaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 164 at io_uring/io_uring.c:3062 io_ring_exit_work+0x39b/0x850 io_uring/io_uring.c:3062
Modules linked in:
CPU: 0 PID: 164 Comm: kworker/u8:5 Not tainted 6.8.0-rc4-next-20240214-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x39b/0x850 io_uring/io_uring.c:3062
Code: 23 e8 c9 0e 24 f6 48 8b 7c 24 10 48 8b 74 24 08 e8 1a b7 0a 00 48 85 c0 75 3d e8 b0 0e 24 f6 e9 96 fd ff ff e8 a6 0e 24 f6 90 <0f> 0b 90 b8 70 17 00 00 48 89 44 24 08 eb cd 44 89 f9 80 e1 07 80
RSP: 0018:ffffc90002e1fa40 EFLAGS: 00010293
RAX: ffffffff8b6fd11a RBX: 000000010000d095 RCX: ffff88801b7cda00
RDX: 0000000000000000 RSI: fffffffffffffffa RDI: 0000000000000000
RBP: ffffc90002e1fbb0 R08: ffffffff8b6fd0ed R09: 1ffff920005c3f38
R10: dffffc0000000000 R11: fffff520005c3f39 R12: 000000010000d08f
R13: ffff88807afd6288 R14: ffff88807afd6538 R15: ffff88807afd6000
FS:  0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f01f05ad988 CR3: 0000000028fc8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 process_one_work kernel/workqueue.c:3146 [inline]
 process_scheduled_works+0x9d7/0x1730 kernel/workqueue.c:3226
 worker_thread+0x86d/0xd70 kernel/workqueue.c:3307
 kthread+0x2f0/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:242
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup