[v6.1] INFO: task hung in blkdev_common_ioctl (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 38fb82ecd144 Linux 6.1.71
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13efefb1e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f8d4b3f2bd71350c
dashboard link: https://syzkaller.appspot.com/bug?extid=eaab1a42ad3fa93f129d
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/44a009057e6d/disk-38fb82ec.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef84f309ccb4/vmlinux-38fb82ec.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c351b9cee4f7/bzImage-38fb82ec.xz

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

INFO: task syz-executor.5:10830 blocked for more than 143 seconds.
Not tainted 6.1.71-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:27560 pid:10830 ppid:3582 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
rwsem_down_write_slowpath+0xea1/0x14b0 kernel/locking/rwsem.c:1189
filemap_invalidate_lock include/linux/fs.h:801 [inline]
blk_ioctl_zeroout block/ioctl.c:184 [inline]
blkdev_common_ioctl+0x151a/0x2350 block/ioctl.c:488
blkdev_ioctl+0x2f5/0x760 block/ioctl.c:611
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbd8327cd29
RSP: 002b:00007fbd840a70c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fbd833abf80 RCX: 00007fbd8327cd29
RDX: 0000000020000080 RSI: 000000000000127f RDI: 0000000000000003
RBP: 00007fbd832c947a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fbd833abf80 R15: 00007ffc8edcd328
</TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12a4f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12acf0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffffffff8d12a320 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:306 [inline]
#0: ffffffff8d12a320 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:747 [inline]
#0: ffffffff8d12a320 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by getty/3301:
#0: ffff88814b213098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
1 lock held by syz-executor.3/3589:
2 locks held by kworker/u4:14/6650:
1 lock held by syz-executor.1/3143:
3 locks held by kworker/1:5/10733:
1 lock held by syz-executor.5/10830:
#0: ffff888148d01ec0 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff888148d01ec0 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:184 [inline]
#0: ffff888148d01ec0 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x151a/0x2350 block/ioctl.c:488
2 locks held by syz-executor.5/12608:

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.71-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 1713 Comm: kworker/u4:0 Not tainted 6.1.71-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet
RIP: 0010:check_kcov_mode kernel/kcov.c:184 [inline]
RIP: 0010:write_comp_data kernel/kcov.c:236 [inline]
RIP: 0010:__sanitizer_cov_trace_const_cmp4+0x30/0x80 kernel/kcov.c:304
Code: 8b 15 d4 d6 77 7e 65 8b 05 d5 d6 77 7e a9 00 01 ff 00 74 10 a9 00 01 00 00 74 5b 83 ba 1c 16 00 00 00 74 52 8b 82 f8 15 00 00 <83> f8 03 75 47 48 8b 8a 00 16 00 00 44 8b 8a fc 15 00 00 49 c1 e1
RSP: 0018:ffffc90005dafa58 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffff888049bed940
RDX: ffff888049bed940 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90005dafb98 R08: ffffffff8a56a620 R09: fffffbfff2092045
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807b343000
R13: ffff888143f9f4c0 R14: dffffc0000000000 R15: ffff88807cdc13e8
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f18067bc000 CR3: 000000000ce8e000 CR4: 00000000003506e0
Call Trace:
<NMI>
</NMI>
<TASK>
rcu_read_unlock include/linux/rcupdate.h:776 [inline]
batadv_iv_ogm_slide_own_bcast_window net/batman-adv/bat_iv_ogm.c:772 [inline]
batadv_iv_ogm_schedule_buff net/batman-adv/bat_iv_ogm.c:826 [inline]
batadv_iv_ogm_schedule+0x660/0x1090 net/batman-adv/bat_iv_ogm.c:869
batadv_iv_send_outstanding_bat_ogm_packet+0x6fa/0x800 net/batman-adv/bat_iv_ogm.c:1713
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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 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 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