[v5.15] INFO: task hung in blkdev_common_ioctl (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 284087d4f7d5 Linux 5.15.158
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=102cd86c980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab74f93e8454887c
dashboard link: https://syzkaller.appspot.com/bug?extid=ea8662f69d178a712dc0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bc1dc4980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13cb0470980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0accc7dacf9d/disk-284087d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb6b5b110f8c/vmlinux-284087d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6763bebdbfea/Image-284087d4.gz.xz

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

INFO: task syz-executor345:4003 blocked for more than 143 seconds.
Not tainted 5.15.158-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor345 state:D stack: 0 pid: 4003 ppid: 3987 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
rwsem_down_write_slowpath+0xd94/0x17e0 kernel/locking/rwsem.c:1165
__down_write_common kernel/locking/rwsem.c:1292 [inline]
__down_write kernel/locking/rwsem.c:1301 [inline]
down_write+0xe8/0x12c kernel/locking/rwsem.c:1552
filemap_invalidate_lock include/linux/fs.h:834 [inline]
blk_ioctl_zeroout block/ioctl.c:183 [inline]
blkdev_common_ioctl+0x1cbc/0x2764 block/ioctl.c:487
blkdev_ioctl+0x350/0xbd0 block/ioctl.c:598
block_ioctl+0xa8/0x114 block/fops.c:493
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:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor345:4004 blocked for more than 143 seconds.
Not tainted 5.15.158-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor345 state:D stack: 0 pid: 4004 ppid: 3990 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
rwsem_down_write_slowpath+0xd94/0x17e0 kernel/locking/rwsem.c:1165
__down_write_common kernel/locking/rwsem.c:1292 [inline]
__down_write kernel/locking/rwsem.c:1301 [inline]
down_write+0xe8/0x12c kernel/locking/rwsem.c:1552
filemap_invalidate_lock include/linux/fs.h:834 [inline]
blk_ioctl_zeroout block/ioctl.c:183 [inline]
blkdev_common_ioctl+0x1cbc/0x2764 block/ioctl.c:487
blkdev_ioctl+0x350/0xbd0 block/ioctl.c:598
block_ioctl+0xa8/0x114 block/fops.c:493
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:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014b114a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311
1 lock held by klogd/3576:
2 locks held by getty/3725:
#0: ffff0000d4318098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e202e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
2 locks held by syz-executor345/3996:
1 lock held by syz-executor345/4003:
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:183 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x1cbc/0x2764 block/ioctl.c:487
1 lock held by syz-executor345/4004:
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:183 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x1cbc/0x2764 block/ioctl.c:487
1 lock held by syz-executor345/4005:
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:183 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x1cbc/0x2764 block/ioctl.c:487
1 lock held by syz-executor345/4012:
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:834 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:183 [inline]
#0: ffff0000c04ad010 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x1cbc/0x2764 block/ioctl.c:487

=============================================



---
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.

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

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.

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