[v5.15] WARNING in del_gendisk

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2ddbd0f967b3 Linux 5.15.102
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1744d352c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d6af46e4bd7d6a2f
dashboard link: https://syzkaller.appspot.com/bug?extid=91df6702a2e1e5b1d250
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=151dde2ac80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10b15826c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d46a989959b6/disk-2ddbd0f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4d06a9b2ddaf/vmlinux-2ddbd0f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0921009430c0/Image-2ddbd0f9.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4052 at block/genhd.c:589 del_gendisk+0x698/0x72c block/genhd.c:589
Modules linked in:
CPU: 0 PID: 4052 Comm: syz-executor351 Not tainted 5.15.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : del_gendisk+0x698/0x72c block/genhd.c:589
lr : del_gendisk+0x698/0x72c block/genhd.c:589
sp : ffff80001c867bc0
x29: ffff80001c867be0 x28: ffff0000c22ad040 x27: 1fffe0001851cc2a
x26: 1fffe00019cb0610 x25: 1ffff0000390cf88 x24: ffff0000ce583080
x23: 0000000000000000 x22: ffff0000ce5830a0 x21: ffff0000ce583000
x20: ffff0000cc506388 x19: 0000000000000240 x18: ffff80001c867740
x17: ff8080000c091a40 x16: ffff8000082ed0d4 x15: 000000000000b5c9
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000a88ab5c x10: 0000000000000000 x9 : ffff80000a88ab5c
x8 : ffff0000c22ad040 x7 : ffff80000c091ca8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800011acdf28
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
del_gendisk+0x698/0x72c block/genhd.c:589
loop_remove drivers/block/loop.c:2426 [inline]
loop_control_remove drivers/block/loop.c:2483 [inline]
loop_control_ioctl+0x4a8/0x62c drivers/block/loop.c:2521
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 <unknown>:584
irq event stamp: 13728
hardirqs last enabled at (13727): [<ffff8000088d2d9c>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (13728): [<ffff800011a03758>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (13126): [<ffff800008020e34>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (13126): [<ffff800008020e34>] __do_softirq+0xcc4/0xf60 kernel/softirq.c:587
softirqs last disabled at (13121): [<ffff8000081b7b48>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (13121): [<ffff8000081b7b48>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (13121): [<ffff8000081b7b48>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 3fc9ebe95e765f78 ]---


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches