syzbot


INFO: task hung in nilfs_segctor_thread

Status: auto-obsoleted due to no activity on 2023/08/20 05:29
Reported-by: syzbot+814f1cd7c4a30fc9e739@syzkaller.appspotmail.com
First crash: 591d, last: 579d
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in nilfs_segctor_thread nilfs2 C 41 645d 747d 0/1 upstream: reported C repro on 2022/11/05 03:06
linux-5.15 INFO: task hung in nilfs_segctor_thread (2) 2 113d 193d 0/3 auto-obsoleted due to no activity on 2024/11/07 22:53
upstream INFO: task hung in nilfs_segctor_thread (3) nilfs 138 99d 124d 0/28 auto-obsoleted due to no activity on 2024/10/22 18:08
upstream INFO: task hung in nilfs_segctor_thread nilfs C error 94 568d 742d 22/28 fixed on 2023/06/08 14:41
linux-4.14 INFO: task hung in nilfs_segctor_thread nilfs2 C 1 644d 644d 0/1 upstream: reported C repro on 2023/02/16 07:03
upstream INFO: task hung in nilfs_segctor_thread (2) nilfs C inconclusive 98 166d 276d 26/28 fixed on 2024/07/09 19:14
linux-6.1 INFO: task hung in nilfs_segctor_thread 40 48d 193d 0/3 upstream: reported on 2024/05/12 09:28

Sample crash report:
INFO: task segctord:9335 blocked for more than 143 seconds.
      Not tainted 5.15.106-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:segctord        state:D stack:28192 pid: 9335 ppid:     2 flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0x12c4/0x4590 kernel/sched/core.c:6372
 schedule+0x11b/0x1f0 kernel/sched/core.c:6455
 rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157
 __down_write_common kernel/locking/rwsem.c:1284 [inline]
 __down_write kernel/locking/rwsem.c:1293 [inline]
 down_write+0x164/0x170 kernel/locking/rwsem.c:1542
 nilfs_transaction_lock+0x25c/0x4f0 fs/nilfs2/segment.c:357
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2488 [inline]
 nilfs_segctor_thread+0x542/0x1140 fs/nilfs2/segment.c:2572
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

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: ffff88814aea7098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900020a32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
6 locks held by syz-executor.5/9327:
1 lock held by segctord/9335:
 #0: ffff88807de742a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_transaction_lock+0x25c/0x4f0 fs/nilfs2/segment.c:357

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.106-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/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+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
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 6057 Comm: kworker/u4:16 Not tainted 5.15.106-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs kernel/rcu/tree.c:330 [inline]
RIP: 0010:rcu_is_watching+0xc/0xa0 kernel/rcu/tree.c:1121
Code: da 4a ac 08 41 f7 c4 00 02 00 00 75 b4 eb b3 e8 ba 4a ac 08 66 2e 0f 1f 84 00 00 00 00 00 41 57 41 56 53 65 ff 05 1c d3 97 7e <e8> 5f 5e ac 08 89 c3 83 f8 08 73 72 49 bf 00 00 00 00 00 fc ff df
RSP: 0018:ffffc90003e4fbd8 EFLAGS: 00000282
RAX: 0000000000000000 RBX: ffff88809609d928 RCX: ffff888023253a00
RDX: ffff888023253a00 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff89f45e41 R09: fffffbfff1f76e15
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000325
R13: dffffc0000000000 R14: ffff8880960bcc80 R15: ffff88807c3a2700
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c02e06b020 CR3: 000000001e840000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rcu_read_lock include/linux/rcupdate.h:697 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
 batadv_nc_worker+0xda/0x5b0 net/batman-adv/network-coding.c:723
 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
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/11 13:57 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nilfs_segctor_thread
2023/04/10 03:54 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in nilfs_segctor_thread
2023/04/22 05:29 linux-5.15.y 3299fb36854f 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in nilfs_segctor_thread
* Struck through repros no longer work on HEAD.