[v5.15] INFO: task hung in nilfs_construct_dsync_segment

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14a3ef72580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=f5b7dc6175a40863358d
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz

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

INFO: task kworker/u4:11:4380 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:11 state:D stack:21880 pid: 4380 ppid: 2 flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:6)
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc87/0x1260 kernel/locking/rwsem.c:1165
nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
nilfs_construct_dsync_segment+0x15a/0x6f0 fs/nilfs2/segment.c:2351
do_writepages+0x476/0x6e0 mm/page-writeback.c:2386
__writeback_single_inode+0x153/0xda0 fs/fs-writeback.c:1657
writeback_sb_inodes+0xa4e/0x1680 fs/fs-writeback.c:1940
wb_writeback+0x45d/0xbe0 fs/fs-writeback.c:2114
wb_do_writeback fs/fs-writeback.c:2257 [inline]
wb_workfn+0x43a/0xf20 fs/fs-writeback.c:2298
process_one_work+0x85f/0x1010 kernel/workqueue.c:2310
worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
INFO: task segctord:6359 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:segctord state:D stack:28856 pid: 6359 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc87/0x1260 kernel/locking/rwsem.c:1165
nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2562 [inline]
nilfs_segctor_thread+0x518/0x1180 fs/nilfs2/segment.c:2647
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
INFO: task syz.6.991:9765 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.991 state:D stack:26992 pid: 9765 ppid: 9353 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
wb_wait_for_completion+0x171/0x290 fs/fs-writeback.c:191
sync_inodes_sb+0x1bd/0x950 fs/fs-writeback.c:2787
iterate_supers+0x11e/0x1d0 fs/super.c:718
ksys_sync+0x9d/0x170 fs/sync.c:102
__ia32_sys_sync+0xa/0x10 fs/sync.c:113
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ffa8e0f5819
RSP: 002b:00007ffa8c34f028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007ffa8e36efa0 RCX: 00007ffa8e0f5819
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffa8e36efa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffa8e36f038 R14: 00007ffa8e36efa0 R15: 00007ffd00392db8
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c31eaa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by udevd/3561:
2 locks held by getty/3947:
#0: ffff88814c236098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900026562e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5df/0x1a70 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/4232:
#0: ffff888016c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
#1: ffffc9000317fd00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
#2: ffffffff8c323528 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#2: ffffffff8c323528 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2d1/0x750 kernel/rcu/tree_exp.h:845
2 locks held by udevd/4328:
#0: ffff8880207bbd18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x157/0xa60 block/bdev.c:820
#1: ffff8880209cb468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_open+0x6a/0x100 drivers/block/loop.c:2056
2 locks held by udevd/4366:
3 locks held by kworker/u4:11/4380:
#0: ffff888142bb0138 ((wq_completion)writeback){+.+.}-{0:0}
, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
#1: ffffc900033dfd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
#2: ffff88801fffd2a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
2 locks held by syz.6.436/6367:
1 lock held by segctord/6359:
#0: ffff88801fffd2a0 (&nilfs->ns_segctor_sem){++++}-{3:3}
, at: nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
2 locks held by syz.6.991/9765:
#0: ffff888069dfe0e0 (&type->s_umount_key#77){.+.+}-{3:3}, at: iterate_supers+0xa4/0x1d0 fs/super.c:716
#1: ffff8880209c07d8 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:362 [inline]
#1: ffff8880209c07d8 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x1a1/0x950 fs/fs-writeback.c:2785
1 lock held by syz-executor/10188:
#0: ffff8880209cb468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xaa/0xb90 drivers/block/loop.c:1366
2 locks held by syz.7.1192/10603:
#0: ffff888069dfe0e0 (&type->s_umount_key#77){.+.+}-{3:3}, at: iterate_supers+0xa4/0x1d0 fs/super.c:716
#1: ffff8880209c07d8 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:362 [inline]
#1: ffff8880209c07d8 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x1a1/0x950 fs/fs-writeback.c:2785
2 locks held by kworker/1:8/10764:
#0: ffff888016c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
#1: ffffc90002f5fd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
3 locks held by dhcpcd-run-hook/11853:

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 6367 Comm: syz.6.436 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:io_serial_in+0x73/0xb0 drivers/tty/serial/8250/8250_port.c:461
Code: e8 b2 81 29 fd 44 89 f9 d3 e3 49 83 c6 40 4c 89 f0 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 f3 8c 6e fd 41 03 1e 89 da ec <0f> b6 c0 5b 41 5c 41 5e 41 5f c3 44 89 f9 80 e1 07 38 c1 7c aa 4c
RSP: 0018:ffffc90003ed70b0 EFLAGS: 00000002
RAX: 1ffffffff2cc0300 RBX: 00000000000003fd RCX: 0000000000000000
RDX: 00000000000003fd RSI: 000000000007ffff RDI: 0000000000080000
RBP: 0000000000000020 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff520007dae0c R12: dffffc0000000000
R13: ffffffff96601aa8 R14: ffffffff96601840 R15: 0000000000000000
FS: 00007f96894a86c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9193ab6a90 CR3: 000000005c0e3000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
serial_in drivers/tty/serial/8250/8250.h:116 [inline]
wait_for_xmitr+0xe9/0x260 drivers/tty/serial/8250/8250_port.c:2069
serial8250_console_putchar+0x1a/0x50 drivers/tty/serial/8250/8250_port.c:3309
uart_console_write+0xaa/0x100 drivers/tty/serial/serial_core.c:1981
serial8250_console_write+0xc46/0x1000 drivers/tty/serial/8250/8250_port.c:3386
call_console_drivers kernel/printk/printk.c:-1 [inline]
console_unlock+0xb9a/0x1120 kernel/printk/printk.c:2744
vprintk_emit+0xc0/0x150 kernel/printk/printk.c:2274
_printk+0xda/0x130 kernel/printk/printk.c:2299
__nilfs_msg+0x2d8/0x3b0 fs/nilfs2/super.c:78
nilfs_clean_segments+0x5b9/0xa30 fs/nilfs2/segment.c:2535
nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:940 [inline]
nilfs_ioctl+0x2052/0x2190 fs/nilfs2/ioctl.c:1304
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f968b26f819
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f96894a8028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f968b4e9090 RCX: 00007f968b26f819
RDX: 0000200000000640 RSI: 0000000040786e88 RDI: 0000000000000005
RBP: 00007f968b305c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f968b4e9128 R14: 00007f968b4e9090 R15: 00007ffd63d28368
</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