syzbot


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: 234d, last: 7d11h
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
d426a46b-29bd-4c0a-b2fb-e80aa46bef0c 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 c69befb30ac10e158cc9d1557b508ee3f0eca1de
f7d73b29-54d2-4f06-984c-112ca08abfa6 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 f250db59430dfb0102692e53ab92e84e82178c3e 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 1316d 1316d 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 1082d 1127d 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 1217d 1217d 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 650d 650d 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 339d 614d 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 1228d 1228d 0/1 upstream: reported on 2023/01/14 13:39
linux-6.1 INFO: task hung in jfs_flush_journal (2) 1 1 349d 349d 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 1096d 1096d 0/3 auto-obsoleted due to no activity on 2023/09/03 18:59

Sample crash report:
INFO: task jfsCommit:129 blocked in I/O wait for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x16ec/0x5620 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7283
 io_schedule+0x7f/0xd0 kernel/sched/core.c:8110
 __lock_metapage fs/jfs/jfs_metapage.c:52 [inline]
 lock_metapage+0x1ff/0x400 fs/jfs/jfs_metapage.c:66
 __get_metapage+0x49a/0xe20 fs/jfs/jfs_metapage.c:749
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x9dd/0x2ca0 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x331/0x440 fs/jfs/inode.c:162
 evict+0x61e/0xb10 fs/inode.c:841
 txLazyCommit fs/jfs/jfs_txnmgr.c:2666 [inline]
 jfs_lazycommit+0x3ef/0xa10 fs/jfs/jfs_txnmgr.c:2735
 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>
INFO: task syz-executor:5599 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor    state:D stack:21984 pid:5599  tgid:5599  ppid:1      task_flags:0x400140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x16ec/0x5620 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7283
 jfs_flush_journal+0x721/0xf50 fs/jfs/jfs_logmgr.c:1561
 jfs_umount+0x171/0x3d0 fs/jfs/jfs_umount.c:59
 jfs_put_super+0x8c/0x190 fs/jfs/super.c:194
 generic_shutdown_super+0x13d/0x2d0 fs/super.c:646
 kill_block_super+0x44/0x90 fs/super.c:1725
 deactivate_locked_super+0xbc/0x130 fs/super.c:476
 cleanup_mnt+0x437/0x4d0 fs/namespace.c:1312
 task_work_run+0x1d9/0x270 kernel/task_work.c:233
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 __exit_to_user_mode_loop kernel/entry/common.c:67 [inline]
 exit_to_user_mode_loop+0xf3/0x4d0 kernel/entry/common.c:98
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline]
 do_syscall_64+0x33e/0xf80 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f855abfe097
RSP: 002b:00007ffeb8aff438 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f855ac921ca RCX: 00007f855abfe097
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffeb8aff4f0
RBP: 00007ffeb8aff4f0 R08: 00007ffeb8b004f0 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffeb8b00580
R13: 00007f855ac921ca R14: 000000000002ac55 R15: 00007ffeb8b005c0
 </TASK>

Showing all locks held in the system:
4 locks held by kworker/u8:1/13:
1 lock held by khungtaskd/38:
 #0: ffffffff8dfc8080 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8dfc8080 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8dfc8080 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
1 lock held by kworker/u8:2/40:
2 locks held by jfsCommit/129:
 #0: ffff888063eb8900 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x2e8/0x2ca0 fs/jfs/jfs_imap.c:889
 #1: ffff888061c4a808 (&jfs_ip->rdwrlock/1){++++}-{4:4}, at: diFree+0x306/0x2ca0 fs/jfs/jfs_imap.c:894
2 locks held by kworker/u8:8/776:
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801a074138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc90005157c40 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90005157c40 (connector_reaper_work){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
3 locks held by kworker/u8:15/3712:
 #0: ffff888032c6f138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888032c6f138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc9000f2cfc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc9000f2cfc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffffffff8f3584b8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8f3584b8 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x124/0x1680 net/ipv6/addrconf.c:4206
2 locks held by getty/5356:
 #0: ffff8880374030a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003cbe2e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x462/0x13a0 drivers/tty/n_tty.c:2211
1 lock held by syz-executor/5599:
 #0: ffff888035ad20d0 (&type->s_umount_key#71){++++}-{4:4}, at: __super_lock fs/super.c:58 [inline]
 #0: ffff888035ad20d0 (&type->s_umount_key#71){++++}-{4:4}, at: __super_lock_excl fs/super.c:73 [inline]
 #0: ffff888035ad20d0 (&type->s_umount_key#71){++++}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:508
2 locks held by syz-executor/5603:
 #0: ffff888034a42480 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff888064c47b08 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1074 [inline]
 #1: ffff888064c47b08 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2914 [inline]
 #1: ffff888064c47b08 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2938 [inline]
 #1: ffff888064c47b08 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: filename_rmdir+0x1cd/0x520 fs/namei.c:5414
2 locks held by kworker/0:5/5718:
3 locks held by kworker/1:5/5724:
 #0: ffff88801a037938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff88801a037938 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3397
 #1: ffffc90005787c40 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3290 [inline]
 #1: ffffc90005787c40 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3397
 #2: ffff88803ebe5280 (&data->fib_lock){+.+.}-{4:4}, at: nsim_fib_event_work+0x222/0x3e0 drivers/net/netdevsim/fib.c:1490
1 lock held by udevd/5796:
 #0: ffff888037dc4480 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
1 lock held by udevd/5798:
1 lock held by udevd/5804:
2 locks held by udevd/6041:
 #0: ffff888037dc4480 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff8880399f99f0 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1074 [inline]
 #1: ffff8880399f99f0 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2914 [inline]
 #1: ffff8880399f99f0 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2938 [inline]
 #1: ffff8880399f99f0 (&type->i_mutex_dir_key#5/1){+.+.}-{4:4}, at: filename_rmdir+0x1cd/0x520 fs/namei.c:5414
1 lock held by syz.0.202/7048:
 #0: ffff888035ad20d0 (&type->s_umount_key#71){++++}-{4:4}, at: __super_lock fs/super.c:60 [inline]
 #0: ffff888035ad20d0 (&type->s_umount_key#71){++++}-{4:4}, at: super_lock+0x2d6/0x3d0 fs/super.c:122
1 lock held by syz-executor/7198:
 #0: ffff8880377f80d0 (&type->s_umount_key#71){++++}-{4:4}, at: __super_lock fs/super.c:58 [inline]
 #0: ffff8880377f80d0 (&type->s_umount_key#71){++++}-{4:4}, at: __super_lock_excl fs/super.c:73 [inline]
 #0: ffff8880377f80d0 (&type->s_umount_key#71){++++}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:508
2 locks held by syz-executor/8347:
 #0: ffffffff8f3584b8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff8f3584b8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock net/core/rtnetlink.c:341 [inline]
 #0: ffffffff8f3584b8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x883/0x1bb0 net/core/rtnetlink.c:4109
 #1: ffff888065f55878 (&wg->device_update_lock){+.+.}-{4:4}, at: wg_open+0x227/0x420 drivers/net/wireguard/device.c:50
5 locks held by syz.6.399/8778:
6 locks held by syz.6.399/8782:
1 lock held by syz.6.399/8808:
 #0: ffff8880638bbf10 (&sb->s_type->i_mutex_key#24){++++}-{4:4}, at: inode_lock include/linux/fs.h:1029 [inline]
 #0: ffff8880638bbf10 (&sb->s_type->i_mutex_key#24){++++}-{4:4}, at: process_measurement+0x457/0x1c90 security/integrity/ima/ima_main.c:300
1 lock held by syz.6.399/8809:
 #0: ffff8880638bbf10 (&sb->s_type->i_mutex_key#24){++++}-{4:4}, at: inode_lock include/linux/fs.h:1029 [inline]
 #0: ffff8880638bbf10 (&sb->s_type->i_mutex_key#24){++++}-{4:4}, at: process_measurement+0x457/0x1c90 security/integrity/ima/ima_main.c:300
2 locks held by syz.3.401/8795:

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 38 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 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+0xfd3/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: 5587 Comm: syz-executor Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:its_return_thunk+0x0/0x10 arch/x86/lib/retpoline.S:417
Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc <c3> cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 e9 eb d4 11 f6 cc
RSP: 0018:ffffc900043074e0 EFLAGS: 00000002
RAX: 000000000022c29d RBX: 0000000000000246 RCX: 0000000080000001
RDX: 0000000000000000 RSI: ffffffff8d607357 RDI: ffffffff8ba75860
RBP: ffffc900043075f0 R08: ffffffff8f8904f7 R09: 1ffffffff1f1209e
R10: dffffc0000000000 R11: fffffbfff1f1209f R12: dffffc0000000000
R13: 1ffff92000860ea8 R14: ffff888035641080 R15: ffff888035641080
FS:  000055558b535540(0000) GS:ffff888126171000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f88f01f1000 CR3: 00000000397ec000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:178 [inline]
 _raw_spin_unlock_irqrestore+0x30/0x80 kernel/locking/spinlock.c:198
 unlock_rt_mutex_safe kernel/locking/rtmutex.c:350 [inline]
 rt_mutex_slowunlock+0x4a7/0x8b0 kernel/locking/rtmutex.c:1463
 free_poll_entry fs/select.c:132 [inline]
 poll_freewait+0xb1/0x240 fs/select.c:141
 do_select+0x1537/0x15c0 fs/select.c:608
 core_sys_select+0x898/0xc30 fs/select.c:677
 do_pselect fs/select.c:770 [inline]
 __do_sys_pselect6 fs/select.c:809 [inline]
 __se_sys_pselect6+0x267/0x320 fs/select.c:800
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa45ce87fd7
Code: 48 89 fa 4c 89 df e8 a8 56 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
RSP: 002b:00007ffdba3081a0 EFLAGS: 00000202 ORIG_RAX: 000000000000010e
RAX: ffffffffffffffda RBX: 000055558b535540 RCX: 00007fa45ce87fd7
RDX: 0000000000000000 RSI: 00007ffdba3082c0 RDI: 0000000000000026
RBP: 00007ffdba308720 R08: 00007ffdba3081e0 R09: 00007ffdba3081f0
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffdba308560
R13: 00007ffdba308350 R14: 585858582e7a7973 R15: 00007ffdba308790
 </TASK>

Crashes (35):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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.