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: 254d, last: 1d07h
✨ 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 1335d 1335d 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 1101d 1146d 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 1236d 1236d 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 670d 670d 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 358d 634d 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 1247d 1247d 0/1 upstream: reported on 2023/01/14 13:39
linux-6.1 INFO: task hung in jfs_flush_journal (2) 1 1 368d 368d 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 1115d 1115d 0/3 auto-obsoleted due to no activity on 2023/09/03 18:59

Sample crash report:
INFO: task syz.0.487:10497 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.487       state:D stack:26968 pid:10497 tgid:10491 ppid:9670   task_flags:0x400040 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x16d8/0x55e0 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7283
 jfs_flush_journal+0x719/0xf50 fs/jfs/jfs_logmgr.c:1561
 jfs_sync_fs+0x7d/0xa0 fs/jfs/super.c:649
 __iterate_supers+0x137/0x240 fs/super.c:927
 ksys_sync fs/sync.c:104 [inline]
 __ia32_sys_sync+0xbe/0x120 fs/sync.c:111
 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:0x7f0ae0ebce59
RSP: 002b:00007f0adf0cc028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f0ae1136180 RCX: 00007f0ae0ebce59
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f0ae1136180 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0ae1136218 R14: 00007f0ae1136180 R15: 00007ffe205a4098
 </TASK>
INFO: task syz.5.488:10523 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.488       state:D stack:25640 pid:10523 tgid:10512 ppid:10024  task_flags:0x400140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x16d8/0x55e0 kernel/sched/core.c:7189
 __schedule_loop kernel/sched/core.c:7268 [inline]
 rt_mutex_schedule+0x76/0xf0 kernel/sched/core.c:7564
 rwbase_write_lock+0x3cf/0x720 kernel/locking/rwbase_rt.c:273
 do_remount fs/namespace.c:3400 [inline]
 path_mount+0xd04/0x1040 fs/namespace.c:4149
 do_mount fs/namespace.c:4170 [inline]
 __do_sys_mount fs/namespace.c:4386 [inline]
 __se_sys_mount+0x31d/0x420 fs/namespace.c:4363
 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:0x7f912ec3e0ca
RSP: 002b:00007f912ce74e58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f912ce74ee0 RCX: 00007f912ec3e0ca
RDX: 0000200000000f40 RSI: 0000200000000f00 RDI: 0000000000000000
RBP: 0000200000000f40 R08: 00007f912ce74ee0 R09: 0000000001a5a438
R10: 0000000001a5a438 R11: 0000000000000246 R12: 0000200000000f00
R13: 00007f912ce74ea0 R14: 0000000000000000 R15: 0000200000004440
 </TASK>

Showing all locks held in the system:
1 lock held by kauditd/37:
1 lock held by khungtaskd/38:
 #0: ffffffff8ddc7b60 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8ddc7b60 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8ddc7b60 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
6 locks held by kworker/u8:8/1157:
5 locks held by kworker/u8:9/1175:
2 locks held by kworker/u8:11/1197:
 #0: ffff888019c34138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888019c34138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3397
 #1: ffffc90005a97c40 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #1: ffffc90005a97c40 (connector_reaper_work){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3397
2 locks held by kworker/u8:13/2334:
 #0: ffff888019c34938 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888019c34938 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3397
 #1: ffffc9000791fc40 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #1: ffffc9000791fc40 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3397
2 locks held by getty/5354:
 #0: ffff888036a1b0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003cc62e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x460/0x1390 drivers/tty/n_tty.c:2211
3 locks held by kworker/u8:17/7993:
 #0: ffff888031966938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #0: ffff888031966938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3397
 #1: ffffc90003bbfc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3289 [inline]
 #1: ffffc90003bbfc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3397
 #2: ffffffff8f1484b8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8f1484b8 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x123/0x16e0 net/ipv6/addrconf.c:4208
1 lock held by syz-executor/9746:
1 lock held by udevd/10476:
 #0: ffff888010e32480 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
1 lock held by syz.0.487/10497:
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: __super_lock fs/super.c:60 [inline]
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: super_lock+0x2d6/0x3d0 fs/super.c:122
1 lock held by syz.5.488/10523:
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: do_remount fs/namespace.c:3400 [inline]
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: path_mount+0xd04/0x1040 fs/namespace.c:4149
1 lock held by syz.9.523/10873:
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: __super_lock fs/super.c:60 [inline]
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: super_lock+0x2d6/0x3d0 fs/super.c:122
1 lock held by syz.9.523/10876:
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: __super_lock fs/super.c:60 [inline]
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: super_lock+0x2d6/0x3d0 fs/super.c:122
1 lock held by syz.3.534/11091:
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: __super_lock fs/super.c:60 [inline]
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: super_lock+0x2d6/0x3d0 fs/super.c:122
1 lock held by syz.3.534/11095:
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: __super_lock fs/super.c:60 [inline]
 #0: ffff8880644a00d0 (&type->s_umount_key#65){++++}-{4:4}, at: super_lock+0x2d6/0x3d0 fs/super.c:122
4 locks held by syz-executor/11184:
 #0: ffff888068088f80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close net/bluetooth/hci_core.c:500 [inline]
 #0: ffff888068088f80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_unregister_dev+0x212/0x5a0 net/bluetooth/hci_core.c:2679
 #1: ffff8880680880b0 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x61f/0x10a0 net/bluetooth/hci_sync.c:5371
 #2: ffff888019c3f348 (&root->kernfs_supers_rwsem){++++}-{4:4}, at: kernfs_remove_by_name_ns+0x3f/0x140 fs/kernfs/dir.c:1792
 #3: ffff888019c3f238 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_remove_by_name_ns+0x4e/0x140 fs/kernfs/dir.c:1793
7 locks held by syz-executor/11494:
1 lock held by syz-executor/11636:
 #0: ffffffff8f1484b8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff8f1484b8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x767/0xc00 net/core/rtnetlink.c:7003
3 locks held by syz-executor/11658:
1 lock held by rm/11784:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 38 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/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+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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 1183 Comm: kworker/u8:10 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:trace_lock_acquire include/trace/events/lock.h:24 [inline]
RIP: 0010:lock_acquire+0x58/0x350 kernel/locking/lockdep.c:5831
Code: 8b 05 bc 09 a8 10 48 89 44 24 58 0f 1f 44 00 00 65 8b 05 bf 09 a8 10 83 f8 08 0f 83 83 01 00 00 89 c0 48 0f a3 05 68 e3 c7 0d <73> 0d e8 41 37 09 00 84 c0 0f 84 ca 01 00 00 83 3d 82 f6 c7 0d 00
RSP: 0018:ffffc90005b67888 EFLAGS: 00000097
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88803e961e10
RBP: ffffffff8b1955a7 R08: 0000000000000001 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1ecf93f R12: 0000000000000000
R13: ffff88803e961e10 R14: 0000000000000000 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff8881264a1000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6fed51de9c CR3: 0000000038238000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:132 [inline]
 _raw_spin_lock_irqsave+0x40/0x60 kernel/locking/spinlock.c:166
 rtlock_slowlock kernel/locking/rtmutex.c:1916 [inline]
 rtlock_lock kernel/locking/spinlock_rt.c:43 [inline]
 __rt_spin_lock kernel/locking/spinlock_rt.c:49 [inline]
 rt_spin_lock+0x157/0x400 kernel/locking/spinlock_rt.c:57
 spin_lock include/linux/spinlock_rt.h:45 [inline]
 skb_dequeue+0x2d/0x150 net/core/skbuff.c:3967
 ieee80211_iface_work+0x173/0x13f0 net/mac80211/iface.c:1843
 cfg80211_wiphy_work+0x2e1/0x490 net/wireless/core.c:513
 process_one_work kernel/workqueue.c:3314 [inline]
 process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3397
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3478
 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>

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