syzbot


INFO: task hung in nilfs_segctor_thread (3)

Status: auto-obsoleted due to no activity on 2024/10/22 18:08
Subsystems: nilfs
[Documentation on labels]
Reported-by: syzbot+377059e0af6136c7d5c4@syzkaller.appspotmail.com
First crash: 161d, last: 129d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [nilfs?] INFO: task hung in nilfs_segctor_thread (3) 0 (1) 2024/07/19 19:17
Similar bugs (8)
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 675d 777d 0/1 upstream: reported C repro on 2022/11/05 03:06
linux-5.15 INFO: task hung in nilfs_segctor_thread (2) 2 143d 223d 0/3 auto-obsoleted due to no activity on 2024/11/07 22:53
upstream INFO: task hung in nilfs_segctor_thread nilfs C error 94 598d 772d 22/28 fixed on 2023/06/08 14:41
linux-5.15 INFO: task hung in nilfs_segctor_thread 3 609d 621d 0/3 auto-obsoleted due to no activity on 2023/08/20 05:29
linux-4.14 INFO: task hung in nilfs_segctor_thread nilfs2 C 1 674d 674d 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 196d 306d 26/28 fixed on 2024/07/09 19:14
linux-6.1 INFO: task hung in nilfs_segctor_thread 40 78d 223d 0/3 auto-obsoleted due to no activity on 2024/12/12 18:46
linux-5.15 INFO: task hung in nilfs_segctor_thread (3) 1 17d 17d 0/3 upstream: reported on 2024/12/03 18:16

Sample crash report:
INFO: task segctord:7368 blocked for more than 143 seconds.
      Not tainted 6.11.0-rc3-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:segctord        state:D stack:28216 pid:7368  tgid:7368  ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5188 [inline]
 __schedule+0x17ae/0x4a10 kernel/sched/core.c:6529
 __schedule_loop kernel/sched/core.c:6606 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6621
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6678
 rwsem_down_write_slowpath+0xeeb/0x13b0 kernel/locking/rwsem.c:1178
 __down_write_common kernel/locking/rwsem.c:1306 [inline]
 __down_write kernel/locking/rwsem.c:1315 [inline]
 down_write+0x1d7/0x220 kernel/locking/rwsem.c:1580
 nilfs_transaction_lock+0x25d/0x4f0 fs/nilfs2/segment.c:357
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2536 [inline]
 nilfs_segctor_thread+0x551/0x11b0 fs/nilfs2/segment.c:2622
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Showing all locks held in the system:
2 locks held by kworker/u8:1/12:
 #0: ffff88801630c948 ((wq_completion)iou_exit){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3206 [inline]
 #0: ffff88801630c948 ((wq_completion)iou_exit){+.+.}-{0:0}, at: process_scheduled_works+0x90a/0x1830 kernel/workqueue.c:3312
 #1: ffffc90000117d00 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3207 [inline]
 #1: ffffc90000117d00 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_scheduled_works+0x945/0x1830 kernel/workqueue.c:3312
1 lock held by khungtaskd/30:
 #0: ffffffff8e7382e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:326 [inline]
 #0: ffffffff8e7382e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8e7382e0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6626
5 locks held by kworker/u8:2/35:
 #0: ffff8880162e3148 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3206 [inline]
 #0: ffff8880162e3148 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x90a/0x1830 kernel/workqueue.c:3312
 #1: ffffc90000ab7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3207 [inline]
 #1: ffffc90000ab7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x945/0x1830 kernel/workqueue.c:3312
 #2: ffffffff8fa632d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x16a/0xcc0 net/core/net_namespace.c:594
 #3: ffffffff8fa6fe48 (rtnl_mutex){+.+.}-{3:3}, at: cleanup_net+0x6af/0xcc0 net/core/net_namespace.c:630
 #4: ffffffff8e73d6b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:296 [inline]
 #4: ffffffff8e73d6b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x381/0x830 kernel/rcu/tree_exp.h:958
3 locks held by kworker/u8:5/1063:
 #0: ffff8880b933e9d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:560
 #1: ffff8880b9328948 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x441/0x770 kernel/sched/psi.c:989
 #2: ffffffff8e7382e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:326 [inline]
 #2: ffffffff8e7382e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #2: ffffffff8e7382e0 (rcu_read_lock){....}-{1:2}, at: batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
 #2: ffffffff8e7382e0 (rcu_read_lock){....}-{1:2}, at: batadv_nc_worker+0xcb/0x610 net/batman-adv/network-coding.c:719
2 locks held by kworker/u8:7/1121:
 #0: ffff88801630c948 ((wq_completion)iou_exit){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3206 [inline]
 #0: ffff88801630c948 ((wq_completion)iou_exit){+.+.}-{0:0}, at: process_scheduled_works+0x90a/0x1830 kernel/workqueue.c:3312
 #1: ffffc90004387d00 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3207 [inline]
 #1: ffffc90004387d00 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_scheduled_works+0x945/0x1830 kernel/workqueue.c:3312
3 locks held by kworker/u8:10/2574:
 #0: ffff888015489148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3206 [inline]
 #0: ffff888015489148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x90a/0x1830 kernel/workqueue.c:3312
 #1: ffffc90009a37d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3207 [inline]
 #1: ffffc90009a37d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_scheduled_works+0x945/0x1830 kernel/workqueue.c:3312
 #2: ffffffff8fa6fe48 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xe/0x60 net/core/link_watch.c:276
2 locks held by dhcpcd/4883:
 #0: ffff88804f6fe678 (nlk_cb_mutex-ROUTE){+.+.}-{3:3}, at: __netlink_dump_start+0x119/0x780 net/netlink/af_netlink.c:2404
 #1: ffffffff8fa6fe48 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:79 [inline]
 #1: ffffffff8fa6fe48 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_dumpit+0x99/0x200 net/core/rtnetlink.c:6506
2 locks held by getty/4971:
 #0: ffff88802b7e90a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f062f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6ac/0x1e00 drivers/tty/n_tty.c:2211
3 locks held by kworker/0:6/5327:
 #0: ffff888015480948 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3206 [inline]
 #0: ffff888015480948 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x90a/0x1830 kernel/workqueue.c:3312
 #1: ffffc900044f7d00 (deferred_process_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3207 [inline]
 #1: ffffc900044f7d00 (deferred_process_work){+.+.}-{0:0}, at: process_scheduled_works+0x945/0x1830 kernel/workqueue.c:3312
 #2: ffffffff8fa6fe48 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xe/0x20 net/switchdev/switchdev.c:104
3 locks held by syz.2.222/7367:
1 lock held by segctord/7368:
 #0: ffff88801caaa2a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_transaction_lock+0x25d/0x4f0 fs/nilfs2/segment.c:357
1 lock held by syz-executor/8745:
 #0: ffffffff8e73d6b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:328 [inline]
 #0: ffffffff8e73d6b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x451/0x830 kernel/rcu/tree_exp.h:958
1 lock held by syz-executor/9250:
 #0: ffffffff8fa6fe48 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:79 [inline]
 #0: ffffffff8fa6fe48 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x6e6/0xcf0 net/core/rtnetlink.c:6644
2 locks held by syz.0.394/9281:

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.11.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119
 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:223 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:379
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 9281 Comm: syz.0.394 Not tainted 6.11.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:unwind_get_return_address+0x46/0xc0 arch/x86/kernel/unwind_orc.c:369
Code: 48 89 d8 48 c1 e8 03 42 0f b6 04 30 84 c0 75 72 8b 2b 31 ff 89 ee e8 69 65 52 00 85 ed 74 4a 48 83 c3 48 49 89 df 49 c1 ef 03 <43> 80 3c 37 00 74 08 48 89 df e8 8b 81 b6 00 48 8b 3b e8 d3 6f 1e
RSP: 0018:ffffc9000314ef38 EFLAGS: 00000a06
RAX: 0000000000000000 RBX: ffffc9000314efa8 RCX: ffff888021659e00
RDX: ffff888021659e00 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff814115c7 R09: ffffffff814130bf
R10: 0000000000000003 R11: ffff888021659e00 R12: ffff888021659e00
R13: ffffffff817f1da0 R14: dffffc0000000000 R15: 1ffff92000629df5
FS:  00007fb6bb6896c0(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb6b1fff000 CR3: 0000000060c7e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 arch_stack_walk+0x125/0x1b0 arch/x86/kernel/stacktrace.c:26
 stack_trace_save+0x118/0x1d0 kernel/stacktrace.c:122
 save_stack+0xfb/0x1f0 mm/page_owner.c:156
 __set_page_owner+0x92/0x800 mm/page_owner.c:320
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1493
 prep_new_page mm/page_alloc.c:1501 [inline]
 get_page_from_freelist+0x2e4c/0x2f10 mm/page_alloc.c:3442
 __alloc_pages_noprof+0x256/0x6c0 mm/page_alloc.c:4700
 alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2263
 folio_alloc_mpol_noprof+0x36/0x50 mm/mempolicy.c:2281
 shmem_alloc_folio mm/shmem.c:1722 [inline]
 shmem_alloc_and_add_folio+0x2cf/0x14f0 mm/shmem.c:1782
 shmem_get_folio_gfp+0x8dc/0x2370 mm/shmem.c:2188
 shmem_get_folio mm/shmem.c:2293 [inline]
 shmem_write_begin+0x170/0x4d0 mm/shmem.c:2898
 generic_perform_write+0x399/0x840 mm/filemap.c:4019
 shmem_file_write_iter+0xfc/0x120 mm/shmem.c:3074
 new_sync_write fs/read_write.c:497 [inline]
 vfs_write+0xa72/0xc90 fs/read_write.c:590
 ksys_write+0x1a0/0x2c0 fs/read_write.c:643
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb6ba9784df
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 c9 8c 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 1c 8d 02 00 48
RSP: 002b:00007fb6bb688df0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000002000000 RCX: 00007fb6ba9784df
RDX: 0000000002000000 RSI: 00007fb6b0000000 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000c712
R10: 000000002000c802 R11: 0000000000000293 R12: 0000000000000003
R13: 00007fb6bb688ef0 R14: 00007fb6bb688eb0 R15: 00007fb6b0000000
 </TASK>

Crashes (138):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/12 21:54 upstream 7c626ce4bae1 842184b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/05 06:10 upstream de9c2c66ad8e 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/05 04:08 upstream a5dbd76a8942 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/05 01:45 upstream a5dbd76a8942 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/04 03:19 upstream defaf1a2113a 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/03 23:51 upstream 17712b7ea075 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/03 19:36 upstream 17712b7ea075 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/03 14:09 upstream 17712b7ea075 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/02 21:03 upstream 1c4246294c98 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/02 15:25 upstream c0ecd6388360 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/02 13:35 upstream c0ecd6388360 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/02 07:47 upstream c0ecd6388360 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/01 05:46 upstream 21b136cc63d2 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/01 04:37 upstream 21b136cc63d2 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/01 01:48 upstream 21b136cc63d2 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/30 22:35 upstream 22f546873149 6fde257d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/30 20:57 upstream 22f546873149 6fde257d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/30 18:16 upstream 94ede2a3e913 6fde257d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/30 10:00 upstream 94ede2a3e913 5187fc86 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/30 01:14 upstream 94ede2a3e913 5187fc86 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/28 14:04 upstream 5437f30d3458 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/28 08:59 upstream 910bfc26d16d 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/28 05:18 upstream 910bfc26d16d 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/27 15:40 upstream 3a7e02c040b1 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/27 10:53 upstream 3a7e02c040b1 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/27 09:12 upstream 3a7e02c040b1 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/26 17:38 upstream 1722389b0d86 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/26 10:04 upstream 1722389b0d86 3f86dfed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/26 06:04 upstream 1722389b0d86 3f86dfed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/25 09:57 upstream c33ffdb70cc6 b24754ac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/17 13:28 upstream 0434dbe32053 215bec2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/15 19:06 upstream 5e0497553643 c605e6a2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/07/13 05:16 upstream 975f3b6da180 eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in nilfs_segctor_thread
2024/08/02 17:02 linux-next 931a3b3bccc9 53683cf2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/08/01 23:06 linux-next 931a3b3bccc9 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/08/01 14:22 linux-next 931a3b3bccc9 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/31 20:39 linux-next 931a3b3bccc9 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/31 05:28 linux-next 931a3b3bccc9 6fde257d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/29 13:55 linux-next 931a3b3bccc9 5187fc86 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/29 09:31 linux-next 931a3b3bccc9 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/29 04:34 linux-next 931a3b3bccc9 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/29 02:27 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/29 00:39 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/28 23:30 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/28 18:31 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/28 16:35 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/28 15:28 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/28 13:59 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/28 06:39 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/28 03:51 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/27 23:00 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/07/27 00:16 linux-next 668d33c9ff92 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in nilfs_segctor_thread
2024/08/13 18:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8867bbd4a056 f21a18ca .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in nilfs_segctor_thread
* Struck through repros no longer work on HEAD.