INFO: task hung in jfs_flush_journal (5)

Status: upstream: reported on 2026/05/01 20:24
Subsystems: jfs
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+139671f0b42887d37af9@syzkaller.appspotmail.com
First crash: 304d, last: 9d04h
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
d426a46b assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ INFO: task hung in jfs_flush_journal (5) 2026/05/26 12:41 2026/05/26 12:41 2026/05/26 13:42 c69befb3

			
		
f7d73b29 assessment-security 💥 INFO: task hung in jfs_flush_journal (5) 2026/05/07 04:59 2026/05/07 08:27 2026/05/07 09:38 f250db59
Error 503, Message: This model is currently experiencing high demand. Spikes in demand are usually temporary. Please try again later., Status: UNAVAILABLE, Details: []
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [jfs?] INFO: task hung in jfs_flush_journal (5) 0 (1) 2026/05/01 20:24
Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in jfs_flush_journal jfs 1 1 1385d 1385d 0/29 auto-obsoleted due to no activity on 2023/01/17 08:27
upstream INFO: task hung in jfs_flush_journal (3) jfs 1 4 1151d 1196d 0/29 auto-obsoleted due to no activity on 2023/09/08 02:21
upstream INFO: task hung in jfs_flush_journal (2) jfs 1 1 1286d 1286d 0/29 auto-obsoleted due to no activity on 2023/04/25 22:54
linux-6.1 INFO: task hung in jfs_flush_journal 1 1 720d 720d 0/3 auto-obsoleted due to no activity on 2024/11/22 04:48
upstream INFO: task hung in jfs_flush_journal (4) jfs 1 45 408d 684d 0/29 auto-obsoleted due to no activity on 2025/09/29 12:32
linux-4.19 INFO: task hung in jfs_flush_journal jfs 1 1 1297d 1297d 0/1 upstream: reported on 2023/01/14 13:39
linux-6.1 INFO: task hung in jfs_flush_journal (2) 1 1 418d 418d 0/3 auto-obsoleted due to no activity on 2025/09/19 18:53
linux-5.15 INFO: task hung in jfs_flush_journal 1 1 1165d 1165d 0/3 auto-obsoleted due to no activity on 2023/09/03 18:59

Sample crash report:
INFO: task syz.6.4868:25627 blocked for more than 144 seconds.
      Tainted: G             L      syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.4868      state:D stack:26808 pid:25627 tgid:25598 ppid:22159  task_flags:0x400140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5510 [inline]
 __schedule+0x17d9/0x56c0 kernel/sched/core.c:7234
 __schedule_loop kernel/sched/core.c:7311 [inline]
 schedule+0x164/0x2b0 kernel/sched/core.c:7326
 jfs_flush_journal+0x719/0xf50 fs/jfs/jfs_logmgr.c:1561
 jfs_sync_fs+0x7d/0xa0 fs/jfs/super.c:650
 sync_filesystem+0x1cf/0x230 fs/sync.c:66
 jfs_reconfigure+0xc6/0x990 fs/jfs/super.c:370
 reconfigure_super+0x232/0x8f0 fs/super.c:1020
 vfs_cmd_reconfigure fs/fsopen.c:268 [inline]
 vfs_fsconfig_locked+0x171/0x320 fs/fsopen.c:297
 __do_sys_fsconfig fs/fsopen.c:463 [inline]
 __se_sys_fsconfig+0x6b9/0x810 fs/fsopen.c:350
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fdc21b9de99
RSP: 002b:00007fdc22b1d028 EFLAGS: 00000246 ORIG_RAX: 00000000000001af
RAX: ffffffffffffffda RBX: 00007fdc21e26090 RCX: 00007fdc21b9de99
RDX: 0000000000000000 RSI: 0000000000000007 RDI: 0000000000000005
RBP: 00007fdc21c33eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fdc21e26128 R14: 00007fdc21e26090 R15: 00007ffe69d3a2c8
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:840 [inline]
 #0: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
2 locks held by getty/5376:
 #0: ffff8880354990a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000322b2e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x45a/0x1360 drivers/tty/n_tty.c:2211
6 locks held by kworker/0:4/5743:
 #0: ffff8880226cdd40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff8880226cdd40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #1: ffffc90003bf7c40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffffc90003bf7c40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #2: ffff8880299111d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #2: ffff8880299111d8 (&dev->mutex){....}-{4:4}, at: hub_event+0x184/0x4d30 drivers/usb/core/hub.c:5899
 #3: ffff888029916568 (&port_dev->status_lock){+.+.}-{4:4}, at: usb_lock_port drivers/usb/core/hub.c:3252 [inline]
 #3: ffff888029916568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5464 [inline]
 #3: ffff888029916568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #3: ffff888029916568 (&port_dev->status_lock){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #3: ffff888029916568 (&port_dev->status_lock){+.+.}-{4:4}, at: hub_event+0x20a1/0x4d30 drivers/usb/core/hub.c:5953
 #4: ffff8880294fef60 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect drivers/usb/core/hub.c:5465 [inline]
 #4: ffff8880294fef60 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
 #4: ffff8880294fef60 (hcd->address0_mutex){+.+.}-{4:4}, at: port_event drivers/usb/core/hub.c:5871 [inline]
 #4: ffff8880294fef60 (hcd->address0_mutex){+.+.}-{4:4}, at: hub_event+0x20c9/0x4d30 drivers/usb/core/hub.c:5953
 #5: ffffffff8f8db288 (ehci_cf_port_reset_rwsem){.+.+}-{4:4}, at: hub_port_reset+0x14d/0x1810 drivers/usb/core/hub.c:3067
3 locks held by kworker/1:7/5788:
 #0: ffff88801b029d40 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff88801b029d40 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #1: ffffc900044e7c40 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffffc900044e7c40 ((reg_check_chans).work){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #2: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: reg_check_chans_work+0xac/0x1110 net/wireless/reg.c:2469
1 lock held by syz-executor/18086:
2 locks held by syz.6.4868/25627:
 #0: ffff888051c04c68 (&fc->uapi_mutex){+.+.}-{4:4}, at: __do_sys_fsconfig fs/fsopen.c:461 [inline]
 #0: ffff888051c04c68 (&fc->uapi_mutex){+.+.}-{4:4}, at: __se_sys_fsconfig+0x68d/0x810 fs/fsopen.c:350
 #1: ffff888069c680d8 (&type->s_umount_key#107){+.+.}-{4:4}, at: vfs_cmd_reconfigure fs/fsopen.c:267 [inline]
 #1: ffff888069c680d8 (&type->s_umount_key#107){+.+.}-{4:4}, at: vfs_fsconfig_locked+0x169/0x320 fs/fsopen.c:297
3 locks held by kworker/u8:3/25992:
 #0: ffff888031a5e940 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff888031a5e940 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #1: ffffc900053efc40 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffffc900053efc40 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #2: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_verify_work+0x19/0x30 net/ipv6/addrconf.c:4769
4 locks held by kworker/u8:35/26271:
 #0: ffff88801c28e140 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff88801c28e140 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #1: ffffc9000422fc40 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffffc9000422fc40 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #2: ffffffff9001e788 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xf5/0x810 net/core/net_namespace.c:673
 #3: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: default_device_exit_batch+0xe5/0x9e0 net/core/dev.c:13085
3 locks held by syz.1.5281/27637:
1 lock held by syz.5.5315/27800:
 #0: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #0: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_dellink+0x41b/0x810 net/core/rtnetlink.c:3635
1 lock held by syz.2.5318/27803:
 #0: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: wext_ioctl_dispatch+0xa2/0x410 net/wireless/wext-core.c:1012
1 lock held by syz.7.5320/27811:
 #0: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: __tun_chr_ioctl+0x3bc/0x1e10 drivers/net/tun.c:3148
2 locks held by syz.1.5316/27837:
 #0: ffff888033e19380 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #0: ffff888033e19380 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: __sock_release net/socket.c:709 [inline]
 #0: ffff888033e19380 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: sock_close+0x82/0x220 net/socket.c:1501
 #1: ffff88804ed915e0 (sk_lock-AF_PHONET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1713 [inline]
 #1: ffff88804ed915e0 (sk_lock-AF_PHONET){+.+.}-{0:0}, at: pep_sock_unhash+0x2a/0x280 net/phonet/pep.c:1343
1 lock held by syz.0.5322/27838:
 #0: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9002d340 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x767/0xc00 net/core/rtnetlink.c:7082
2 locks held by syz.0.5322/27839:
 #0: ffff888078d40dc0 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #0: ffff888078d40dc0 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: __sock_release net/socket.c:709 [inline]
 #0: ffff888078d40dc0 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: sock_close+0x82/0x220 net/socket.c:1501
 #1: ffffffff8eb5ff68 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:311 [inline]
 #1: ffffffff8eb5ff68 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2d0/0x770 kernel/rcu/tree_exp.h:961

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 31 Comm: khungtaskd Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:122
 nmi_trigger_cpumask_backtrace+0x17a/0x380 lib/nmi_backtrace.c:65
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x135/0x170 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:353 [inline]
 watchdog+0xfd7/0x1030 kernel/hung_task.c:561
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:pv_native_safe_halt+0xf/0x20 arch/x86/kernel/paravirt.c:64
Code: fc 7e 02 e9 fe 7f 3f f5 cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 0f 00 2d 53 ae 18 00 fb f4 <e9> d7 7f 3f f5 cc cc cc cc cc cc cc cc cc cc cc cc 90 90 90 90 90
RSP: 0018:ffffffff8e807de0 EFLAGS: 00000246
RAX: 00000000025bfdf9 RBX: ffffffff819b4450 RCX: 0000000080000001
RDX: 0000000000000001 RSI: ffffffff8e22c582 RDI: ffffffff8c4bdc80
RBP: ffffffff8e807eb8 R08: ffff8880b86338db R09: 1ffff110170c671b
R10: dffffc0000000000 R11: ffffed10170c671c R12: 0000000000000000
R13: 1ffffffff1d11de8 R14: 1ffffffff1d00fc4 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888124f50000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff43589dbc CR3: 000000004ee10000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 arch_safe_halt arch/x86/kernel/process.c:767 [inline]
 default_idle+0x9/0x20 arch/x86/kernel/process.c:768
 default_idle_call+0x72/0xb0 kernel/sched/idle.c:122
 cpuidle_idle_call kernel/sched/idle.c:199 [inline]
 do_idle+0x2e0/0x540 kernel/sched/idle.c:355
 cpu_startup_entry+0x43/0x60 kernel/sched/idle.c:454
 rest_init+0x2de/0x300 init/main.c:717
 start_kernel+0x392/0x3e0 init/main.c:1175
 x86_64_start_reservations+0x24/0x30 arch/x86/kernel/head64.c:310
 x86_64_start_kernel+0x137/0x1b0 arch/x86/kernel/head64.c:291
 common_startup_64+0x13e/0x157
 </TASK>

Crashes (50):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/26 07:33 upstream 3dab139d4795 492bab15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/07/23 07:43 upstream 4539944e5151 881ce5c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/07/16 18:51 upstream 37e2f878a7a6 71b49442 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/07/12 09:46 upstream 44696aa3a489 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/07/10 10:13 upstream a635d6748234 4167ee25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/07/07 01:12 upstream 8cdeaa50eae8 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/07/05 18:19 upstream f105f3631d51 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/07/05 13:18 upstream 7404ce516372 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/07/05 12:00 upstream 7404ce516372 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/07/05 11:50 upstream 7404ce516372 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/07/03 19:51 upstream 71dfdfb0209b 58bf2096 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/07/01 03:13 upstream dc59e4fea9d8 00a5cf1c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/06/14 04:17 upstream 2b07ea76fd28 1d2f3589 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/06/09 18:25 upstream 2d3090a8aeb5 c36c07f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/05/19 15:21 upstream ab5fce87a778 223544dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/05/17 10:41 upstream 6916d5703ddf de5aae85 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/05/06 19:51 upstream 74fe02ce122a 1dddfd3d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/05/02 05:09 upstream 6fe0be6dc7fa 753c55b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/28 19:07 upstream dca922e019dd ce741359 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/27 20:20 upstream 254f49634ee1 0f700595 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/25 16:35 upstream 27d128c1cff6 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/25 08:57 upstream 27d128c1cff6 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/24 22:11 upstream dd6c438c3e64 1c2b9291 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/24 09:50 upstream 45dcf5e28813 9cfb3ca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/23 09:45 upstream 2a4c0c11c019 b10da5ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/23 09:44 upstream 2a4c0c11c019 b10da5ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/21 01:59 upstream a5d1079c28a5 e65da4ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/20 09:14 upstream c1f49dea2b8f 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/17 18:53 upstream 43cfbdda5af6 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/03/25 21:55 upstream bbeb83d3182a c6143aac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/03/07 15:53 upstream 4ae12d8bd9a8 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/03/06 11:21 upstream 5ee8dbf54602 31e9c887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/02/03 03:23 upstream dee65f79364c d78927dd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2025/11/15 13:27 upstream 7a0892d2836e f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2025/11/05 22:32 upstream 1c353dc8d962 a6c9c731 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jfs_flush_journal
2025/10/18 13:36 upstream f406055cb18c 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2025/10/04 07:39 upstream 9b0d551bcc05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in jfs_flush_journal
2026/04/22 17:40 linux-next 70c8a7ec6715 4595e353 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/18 02:32 linux-next c7275b05bc42 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/18 02:09 linux-next c7275b05bc42 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/18 02:08 linux-next c7275b05bc42 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/18 01:58 linux-next c7275b05bc42 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/18 01:55 linux-next c7275b05bc42 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/18 01:55 linux-next c7275b05bc42 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/18 00:55 linux-next c7275b05bc42 24ecfc1e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/04/06 07:37 linux-next cc13002a9f98 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/03/23 18:19 linux-next 785f0eb2f85d 5e3db351 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2025/12/22 06:06 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jfs_flush_journal
2026/01/11 12:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59e4d31a0470 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in jfs_flush_journal
* Struck through repros no longer work on HEAD.