Hello,
syzbot found the following issue on:
HEAD commit: c957cbb87315 Linux 5.15.105
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=12732b2ec80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=852dc3de44ba1f3f
dashboard link:
https://syzkaller.appspot.com/bug?extid=ec2b0cb78dce7ef062f6
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/91d0cf1fc5fb/disk-c957cbb8.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/346dc1169521/vmlinux-c957cbb8.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/f7005bdc0e20/Image-c957cbb8.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+ec2b0c...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6561 at io_uring/io_uring.c:9682 io_ring_exit_work+0x228/0x126c
Modules linked in:
CPU: 1 PID: 6561 Comm: kworker/u4:17 Not tainted 5.15.105-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events_unbound io_ring_exit_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : io_ring_exit_work+0x228/0x126c
lr : io_ring_exit_work+0x224/0x126c io_uring/io_uring.c:9682
sp : ffff8000209579a0
x29: ffff800020957b00 x28: 1fffe00019b27494 x27: 0000000000001770
x26: ffff80000a8ec60c x25: ffff0000cd93a4a0 x24: ffff0000cd93a000
x23: dfff800000000000 x22: 000000010000c3a4 x21: ffff0000cd93a920
x20: ffff800020957a40 x19: ffffffffffffffff x18: 1fffe00036903f8e
x17: 1fffe00036903f8e x16: ffff80000824bf58 x15: ffff80001495eda0
x14: 1ffff0000291806a x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000a91bf58 x10: 0000000000000000 x9 : ffff80000a91bf58
x8 : ffff0000d62e8000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff800008301f6c
x2 : 0000000000000001 x1 : ffffffffffffffff x0 : 0000000000000000
Call trace:
io_ring_exit_work+0x228/0x126c
process_one_work+0x790/0x11b8 kernel/workqueue.c:2306
worker_thread+0x910/0x1034 kernel/workqueue.c:2453
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
irq event stamp: 925884
hardirqs last enabled at (925883): [<ffff800011a13230>] __raw_spin_unlock_irq include/linux/spinlock_api_smp.h:168 [inline]
hardirqs last enabled at (925883): [<ffff800011a13230>] _raw_spin_unlock_irq+0x9c/0x134 kernel/locking/spinlock.c:202
hardirqs last disabled at (925884): [<ffff80001193ad90>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (879558): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (879558): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (879309): [<ffff8000081b4ee0>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (879309): [<ffff8000081b4ee0>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (879309): [<ffff8000081b4ee0>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 52872ef836263cb7 ]---
---
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.