loop5: detected capacity change from 224 to 0
==================================================================
BUG: KASAN: global-out-of-bounds in record_print_text+0x3aa/0x3e0 kernel/printk/printk.c:1401
Write of size 1 at addr ffffffff8f934daa by task syz-executor.5/12468

CPU: 1 PID: 12468 Comm: syz-executor.5 Not tainted 5.11.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x183/0x22e lib/dump_stack.c:120
 print_address_description+0x5f/0x3b0 mm/kasan/report.c:230
 __kasan_report mm/kasan/report.c:396 [inline]
 kasan_report+0x15e/0x200 mm/kasan/report.c:413
 record_print_text+0x3aa/0x3e0 kernel/printk/printk.c:1401
 console_unlock+0x6f6/0xda0 kernel/printk/printk.c:2555
 vprintk_emit+0x1b2/0x270 kernel/printk/printk.c:2092
 printk+0xc0/0x103 kernel/printk/printk.c:2140
 set_capacity_and_notify+0x22f/0x2c0 block/genhd.c:75
 loop_set_size drivers/block/loop.c:254 [inline]
 loop_configure+0x10b0/0x15b0 drivers/block/loop.c:1161
 lo_ioctl+0x76a/0x21e0 drivers/block/loop.c:1687
 blkdev_ioctl+0x335/0x670 block/ioctl.c:576
 block_ioctl+0xae/0xf0 fs/block_dev.c:1650
 vfs_ioctl fs/ioctl.c:48 [inline]
 __do_sys_ioctl fs/ioctl.c:753 [inline]
 __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:739
 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e087
Code: 48 83 c4 08 48 89 d8 5b 5d c3 66 0f 1f 84 00 00 00 00 00 48 89 e8 48 f7 d8 48 39 c3 0f 92 c0 eb 92 66 90 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 6d b5 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f87da3f8a18 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000006 RCX: 000000000045e087
RDX: 0000000000000005 RSI: 0000000000004c00 RDI: 0000000000000006
RBP: 0000000000000000 R08: 0000000020001548 R09: 0000000000000000
R10: 000000000000e000 R11: 0000000000000246 R12: 0000000000000003
R13: 0000000000000005 R14: 0000000000000005 R15: 0000000020001558

The buggy address belongs to the variable:
 console_owner+0x2a/0x40

Memory state around the buggy address:
 ffffffff8f934c80: 01 f9 f9 f9 f9 f9 f9 f9 01 f9 f9 f9 f9 f9 f9 f9
 ffffffff8f934d00: 00 00 f9 f9 f9 f9 f9 f9 00 00 f9 f9 f9 f9 f9 f9
>ffffffff8f934d80: 00 f9 f9 f9 f9 f9 f9 f9 01 f9 f9 f9 f9 f9 f9 f9
                                  ^
 ffffffff8f934e00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffffff8f934e80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================