INFO: task syz-executor.4:17773 blocked for more than 143 seconds.
Not tainted 5.15.108-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:24224 pid:17773 ppid: 3626 flags:0x00004004
Call Trace:
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
io_schedule+0x88/0x100 kernel/sched/core.c:8472
bit_wait_io+0xe/0xc0 kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xbf/0x1a0 kernel/sched/wait_bit.c:90
out_of_line_wait_on_bit_lock+0x1d0/0x250 kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
__lock_buffer fs/buffer.c:69 [inline]
lock_buffer include/linux/buffer_head.h:402 [inline]
__sync_dirty_buffer+0x120/0x380 fs/buffer.c:3144
__ext4_handle_dirty_metadata+0x288/0x800 fs/ext4/ext4_jbd2.c:381
ext4_handle_dirty_dirblock+0x35e/0x6f0 fs/ext4/namei.c:438
ext4_finish_convert_inline_dir+0x57b/0x6f0 fs/ext4/inline.c:1188
ext4_convert_inline_data_nolock+0xa15/0xda0 fs/ext4/inline.c:1265
ext4_try_add_inline_entry+0x805/0xb60 fs/ext4/inline.c:1338
ext4_add_entry+0x6c2/0x12b0 fs/ext4/namei.c:2384
ext4_add_nondir+0x98/0x290 fs/ext4/namei.c:2771
ext4_create+0x372/0x550 fs/ext4/namei.c:2816
lookup_open fs/namei.c:3392 [inline]
open_last_lookups fs/namei.c:3462 [inline]
path_openat+0x12f6/0x2f20 fs/namei.c:3669
do_filp_open+0x21c/0x460 fs/namei.c:3699
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_open fs/open.c:1235 [inline]
__se_sys_open fs/open.c:1231 [inline]
__x64_sys_open+0x221/0x270 fs/open.c:1231
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f8b9c73d169
RSP: 002b:00007f8b9292b168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f8b9c85d2c0 RCX: 00007f8b9c73d169
RDX: 0000000000000000 RSI: 000000000014d27e RDI: 0000000020000180
RBP: 00007f8b9c798ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffeb6b8616f R14: 00007f8b9292b300 R15: 0000000000022000
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91b920 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3267:
#0: ffff88814ae81098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025132e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
2 locks held by syz-executor.3/3635:
#0: ffff88801c205118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xfb/0x790 block/bdev.c:912
#1: ffff88801c1ef468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xbe0 drivers/block/loop.c:1365
2 locks held by syz-executor.2/3641:
#0: ffff88801c2f0918 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xfb/0x790 block/bdev.c:912
#1: ffff888147236468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xbe0 drivers/block/loop.c:1365
3 locks held by syz-executor.4/17773:
#0: ffff88801e884460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377
#1: ffff888039d303f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff888039d303f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: open_last_lookups fs/namei.c:3459 [inline]
#1: ffff888039d303f0 (&type->i_mutex_dir_key#4){++++}-{3:3}, at: path_openat+0x824/0x2f20 fs/namei.c:3669
#2: ffff888039d300c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff888039d300c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_add_inline_entry+0xf2/0xb60 fs/ext4/inline.c:1296
2 locks held by syz-executor.5/20865:
#0: ffff88802552b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:964 [inline]
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:984 [inline]
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write+0x468/0x920 drivers/tty/tty_io.c:1110
2 locks held by syz-executor.4/20874:
#0: ffff88802552b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:964 [inline]
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:984 [inline]
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write+0x468/0x920 drivers/tty/tty_io.c:1110
2 locks held by syz-executor.4/20875:
#0: ffff88802552b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:964 [inline]
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: do_tty_write drivers/tty/tty_io.c:984 [inline]
#1: ffff88802552b130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: file_tty_write+0x468/0x920 drivers/tty/tty_io.c:1110
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.108-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 904 Comm: kworker/u4:4 Not tainted 5.15.108-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:hlock_class kernel/locking/lockdep.c:197 [inline]
RIP: 0010:mark_lock+0xa0/0x340 kernel/locking/lockdep.c:4568
Code: 02 00 00 8b 1b 81 e3 ff 1f 00 00 89 d8 c1 e8 06 48 8d 3c c5 a0 60 bb 8f be 08 00 00 00 e8 58 6f 66 00 48 0f a3 1d 90 bb 58 0e <73> 11 48 8d 04 5b 48 c1 e0 06 48 8d 98 a0 bf 8a 8f eb 23 48 c7 c0
RSP: 0000:ffffc90004a9f978 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 000000000000072e RCX: ffffffff8162a508
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8fbb6180
RBP: 0000000000000006 R08: dffffc0000000000 R09: fffffbfff1f76c31
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801ca56140
R13: dffffc0000000000 R14: 0000000000000040 R15: ffff88801ca56120
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c0271d4000 CR3: 0000000022db9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
mark_held_locks kernel/locking/lockdep.c:4192 [inline]
__trace_hardirqs_on_caller kernel/locking/lockdep.c:4218 [inline]
lockdep_hardirqs_on_prepare+0x3a0/0x7a0 kernel/locking/lockdep.c:4277
trace_hardirqs_on+0x67/0x80 kernel/trace/trace_preemptirq.c:49
__local_bh_enable_ip+0x164/0x1f0 kernel/softirq.c:388
spin_unlock_bh include/linux/spinlock.h:408 [inline]
batadv_nc_purge_paths+0x30e/0x3b0 net/batman-adv/network-coding.c:475
batadv_nc_worker+0x2cf/0x5b0 net/batman-adv/network-coding.c:724
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298