syzbot


INFO: task hung in jbd2_journal_commit_transaction (5)

Status: upstream: reported C repro on 2024/05/15 03:54
Subsystems: usb ext4
[Documentation on labels]
Reported-by: syzbot+3071bdd0a9953bc0d177@syzkaller.appspotmail.com
First crash: 107d, last: 9h18m
Cause bisection: failed (error log, bisect log)
  
Discussions (3)
Title Replies (including bot) Last reply
[syzbot] Monthly ext4 report (Jul 2024) 0 (1) 2024/07/15 14:03
[syzbot] Monthly ext4 report (Jun 2024) 0 (1) 2024/06/14 08:14
[syzbot] [ext4?] INFO: task hung in jbd2_journal_commit_transaction (5) 0 (2) 2024/05/20 02:41
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in jbd2_journal_commit_transaction (2) ext4 1 1231d 1231d 0/27 auto-closed as invalid on 2021/06/09 10:13
android-44 INFO: task hung in jbd2_journal_commit_transaction C 6 2216d 1929d 0/2 public: reported C repro on 2019/04/13 00:00
android-49 INFO: task hung in jbd2_journal_commit_transaction 5 2124d 2268d 0/3 auto-closed as invalid on 2019/03/29 12:13
linux-6.1 INFO: task hung in jbd2_journal_commit_transaction 1 419d 419d 0/3 auto-obsoleted due to no activity on 2023/09/09 09:50
upstream INFO: task hung in jbd2_journal_commit_transaction (4) ext4 7 362d 510d 0/27 auto-obsoleted due to no activity on 2023/10/25 18:13
upstream INFO: task hung in jbd2_journal_commit_transaction (3) ext4 C error error 24 664d 948d 0/27 auto-obsoleted due to no activity on 2023/01/27 09:20
upstream INFO: task hung in jbd2_journal_commit_transaction ext4 C 52 2110d 2130d 0/27 closed as dup on 2018/10/02 14:53
android-414 INFO: task hung in jbd2_journal_commit_transaction C 31 2115d 1931d 0/1 public: reported C repro on 2019/04/11 00:00

Sample crash report:
INFO: task jbd2/sda1-8:4509 blocked for more than 143 seconds.
      Not tainted 6.10.0-rc2-syzkaller-00269-g96e09b8f8166 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jbd2/sda1-8     state:D
 stack:24904 pid:4509  tgid:4509  ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5408 [inline]
 __schedule+0x17e8/0x4a20 kernel/sched/core.c:6745
 __schedule_loop kernel/sched/core.c:6822 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6837
 io_schedule+0x8d/0x110 kernel/sched/core.c:9043
 bit_wait_io+0x12/0xd0 kernel/sched/wait_bit.c:209
 __wait_on_bit+0xb0/0x2f0 kernel/sched/wait_bit.c:49
 out_of_line_wait_on_bit+0x1d5/0x260 kernel/sched/wait_bit.c:64
 wait_on_buffer include/linux/buffer_head.h:415 [inline]
 journal_wait_on_commit_record fs/jbd2/commit.c:171 [inline]
 jbd2_journal_commit_transaction+0x3d7f/0x6760 fs/jbd2/commit.c:887
 kjournald2+0x463/0x850 fs/jbd2/journal.c:201
 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:
1 lock held by khungtaskd/30:
 #0: 
ffffffff8e333fa0
 (
rcu_read_lock
){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]
){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:781 [inline]
){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6614
5 locks held by kworker/1:1/45:
6 locks held by kworker/1:2/784:
2 locks held by getty/4843:
 #0: ffff88802b05f0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f0e2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}
, at: n_tty_read+0x6b5/0x1e10 drivers/tty/n_tty.c:2201
1 lock held by syz-executor359/5106:
 #0: 
ffff888015ed6948
 (
&root->kernfs_rwsem
){++++}-{3:3}
, at: kernfs_dop_revalidate+0xd4/0x560 fs/kernfs/dir.c:1159
1 lock held by syz-executor359/5107:
 #0: 
ffff888015ed6948
 (
&root->kernfs_rwsem
){++++}-{3:3}
, at: kernfs_dop_revalidate+0xd4/0x560 fs/kernfs/dir.c:1159
1 lock held by syz-executor359/5110:
 #0: ffff888015ed6948 (&root->kernfs_rwsem){++++}-{3:3}, at: kernfs_dop_revalidate+0xd4/0x560 fs/kernfs/dir.c:1159
1 lock held by syz-executor359/5111:
 #0: ffff888015ed6948 (&root->kernfs_rwsem){++++}-{3:3}, at: kernfs_dop_revalidate+0xd4/0x560 fs/kernfs/dir.c:1159
1 lock held by syz-executor359/5113:
 #0: 
ffff888015ed6948 (&root->kernfs_rwsem){++++}-{3:3}, at: kernfs_dop_revalidate+0xd4/0x560 fs/kernfs/dir.c:1159
7 locks held by kworker/1:3/5127:
4 locks held by udevd/5142:
 #0: ffff8880289ba1c8 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xb7/0xd60 fs/seq_file.c:182
 #1: ffff88801e4c1088 (&of->mutex#2){+.+.}-{3:3}, at: kernfs_seq_start+0x53/0x3b0 fs/kernfs/file.c:154
 #2: 
ffff88802ed8ef08
 (
kn->active
#20
){++++}-{0:0}
, at: kernfs_seq_start+0x72/0x3b0 fs/kernfs/file.c:155
 #3: ffff88802cf93190 (&dev->mutex){....}-{3:3}, at: device_lock_interruptible include/linux/device.h:1014 [inline]
 #3: ffff88802cf93190 (&dev->mutex){....}-{3:3}, at: manufacturer_show+0x26/0xa0 drivers/usb/core/sysfs.c:142
1 lock held by syz-executor359/5169:
 #0: ffff888015ed6948 (&root->kernfs_rwsem){++++}-{3:3}, at: kernfs_remove_by_name_ns+0x7a/0x160 fs/kernfs/dir.c:1689

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

NMI backtrace for cpu 0
CPU: 0 PID: 30 Comm: khungtaskd Not tainted 6.10.0-rc2-syzkaller-00269-g96e09b8f8166 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
 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+0xfde/0x1020 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 0 to CPUs 1:
yealink 2-1:36.0: urb_irq_callback - urb status -71
NMI backtrace for cpu 1
CPU: 1 PID: 5127 Comm: kworker/1:3 Not tainted 6.10.0-rc2-syzkaller-00269-g96e09b8f8166 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Workqueue: events_power_efficient gc_worker
RIP: 0010:io_serial_out+0x7e/0xc0 drivers/tty/serial/8250/8250_port.c:413
Code: fc 89 e9 41 d3 e7 48 83 c3 40 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 8c 8b bf fc 44 03 3b 44 89 f0 44 89 fa ee <5b> 41 5c 41 5e 41 5f 5d c3 cc cc cc cc 89 e9 80 e1 07 38 c1 7c a7
RSP: 0018:ffffc90000a18090 EFLAGS: 00000002
RAX: 0000000000000020 RBX: ffffffff94ad1200 RCX: 0000000000000000
RDX: 00000000000003f8 RSI: 0000000000000000 RDI: 0000000000000020
RBP: 0000000000000000 R08: ffffffff853c5d3b R09: 1ffff11003f1e046
R10: dffffc0000000000 R11: ffffffff853c5cf0 R12: dffffc0000000000
R13: 0000000000000020 R14: 0000000000000020 R15: 00000000000003f8
FS:  0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd221d53828 CR3: 000000007cec8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <IRQ>
 serial8250_console_write+0x1212/0x1770 drivers/tty/serial/8250/8250_port.c:3393
 console_emit_next_record kernel/printk/printk.c:2928 [inline]
 console_flush_all+0x865/0xfd0 kernel/printk/printk.c:2994
 console_unlock+0x13b/0x4d0 kernel/printk/printk.c:3063
 vprintk_emit+0x5a6/0x770 kernel/printk/printk.c:2345
 dev_vprintk_emit+0x2ae/0x330 drivers/base/core.c:4951
 dev_printk_emit+0xdd/0x120 drivers/base/core.c:4962
 _dev_err+0x122/0x170 drivers/base/core.c:5017
 urb_irq_callback+0x37e/0x5b0 drivers/input/misc/yealink.c:416
 __usb_hcd_giveback_urb+0x373/0x530 drivers/usb/core/hcd.c:1648
 dummy_timer+0x830/0x45d0 drivers/usb/gadget/udc/dummy_hcd.c:1987
 __run_hrtimer kernel/time/hrtimer.c:1687 [inline]
 __hrtimer_run_queues+0x59b/0xd50 kernel/time/hrtimer.c:1751
 hrtimer_interrupt+0x396/0x990 kernel/time/hrtimer.c:1813
 local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1032 [inline]
 __sysvec_apic_timer_interrupt+0x110/0x3f0 arch/x86/kernel/apic/apic.c:1049
 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]
 sysvec_apic_timer_interrupt+0xa1/0xc0 arch/x86/kernel/apic/apic.c:1043
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
RIP: 0010:seqcount_lockdep_reader_access+0x1e0/0x220 include/linux/seqlock.h:75
Code: f7 4d 85 ed 75 16 e8 af 74 f5 f7 eb 15 e8 a8 74 f5 f7 e8 e3 d5 e5 01 4d 85 ed 74 ea e8 99 74 f5 f7 fb 48 c7 04 24 0e 36 e0 45 <4b> c7 04 3c 00 00 00 00 66 43 c7 44 3c 09 00 00 43 c6 44 3c 0b 00
RSP: 0018:ffffc900037779a0 EFLAGS: 00000293
RAX: ffffffff89a0b1e7 RBX: 0000000000000000 RCX: ffff888029e01e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003777a50 R08: ffffffff89a0b1bd R09: 1ffffffff25f56c2
R10: dffffc0000000000 R11: fffffbfff25f56c3 R12: dffffc0000000000
R13: 0000000000000200 R14: 0000000000000046 R15: 1ffff920006eef34
 nf_conntrack_get_ht include/net/netfilter/nf_conntrack.h:345 [inline]
 gc_worker+0x316/0x1530 net/netfilter/nf_conntrack_core.c:1488
 process_one_work kernel/workqueue.c:3231 [inline]
 process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
 worker_thread+0x86d/0xd70 kernel/workqueue.c:3393
 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>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 2.391 msecs
yealink 2-1:36.0: unexpected response 0
yealink 2-1:36.0: urb_ctl_callback - urb status -71

Crashes (258):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/06/08 09:30 upstream 96e09b8f8166 82c05ab8 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/06/07 05:52 upstream 8a92980606e3 121701b6 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/06/04 11:02 upstream f06ce441457d a1feae05 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/06/02 21:33 upstream 83814698cf48 3113787f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/06/01 05:16 upstream d8ec19857b09 3113787f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/01 20:18 linux-next 0e1980c40b6e 3113787f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/05/20 02:41 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing 51474ab44abf c0f1611a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in jbd2_journal_commit_transaction
2024/05/13 16:21 linux-next 6ba6c795dc73 9026e142 .config console log report syz [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/24 05:56 upstream 28bbe4ea686a 57b2edb1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/24 03:22 upstream 28bbe4ea686a 57b2edb1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/23 14:11 upstream 66ebbdfdeb09 708c10c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/23 12:54 upstream 66ebbdfdeb09 708c10c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/07/23 06:24 upstream 66ebbdfdeb09 708c10c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/22 14:17 upstream 933069701c1b f063dfd9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/22 03:18 upstream 7846b618e0a4 b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/21 00:40 upstream 3c3ff7be9729 b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/07/20 20:09 upstream 3c3ff7be9729 b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/20 08:47 upstream d7e78951a8b8 b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/19 13:08 upstream 68b59730459e ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/07/18 11:39 upstream b1bc554e009e 7403ec00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/17 04:12 upstream 408323581b72 215bec2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/16 11:18 upstream d67978318827 b66b37bd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/15 16:18 upstream 0c3836482481 efee4ed2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/15 08:26 upstream 0c3836482481 c605e6a2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/07/15 03:39 upstream 0c3836482481 eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/15 00:54 upstream 4d145e3f830b eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/14 21:48 upstream 4d145e3f830b eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/14 13:18 upstream 4d145e3f830b eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/10 12:40 upstream 34afb82a3c67 e7213be3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/10 08:17 upstream 34afb82a3c67 79d68ada .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/10 00:12 upstream 34afb82a3c67 79d68ada .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/09 16:18 upstream 4376e966ecb7 79d68ada .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/07 21:00 upstream c6653f49e4fd bc4ebbb5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/07/07 14:53 upstream c6653f49e4fd bc4ebbb5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/07/06 01:09 upstream d270dd21bee0 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 17:27 upstream 661e504db04c 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 17:27 upstream 661e504db04c 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 15:01 upstream 661e504db04c 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 13:47 upstream 661e504db04c 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 12:34 upstream 661e504db04c 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 11:07 upstream 661e504db04c 2a40360c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 07:56 upstream 661e504db04c dc6bbff0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/05 06:15 upstream 661e504db04c dc6bbff0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/04 15:10 upstream 795c58e4c7fc dc6bbff0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/04 01:57 upstream 8a9c6c40432e 409d975c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/07/03 18:09 upstream e9d22f7a6655 409d975c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/03 11:00 upstream e9d22f7a6655 1ecfa2d8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/30 09:26 upstream 8282d5af7be8 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/28 16:50 upstream 5bbd9b249880 b62c7d46 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/28 15:49 upstream 5bbd9b249880 b62c7d46 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/28 11:36 upstream 5bbd9b249880 b62c7d46 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/27 22:29 upstream 6d6444ba8205 b62c7d46 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/27 04:06 upstream 24ca36a562d6 880c1ca1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in jbd2_journal_commit_transaction
2024/06/26 05:48 upstream 55027e689933 dec8bc94 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/25 03:21 upstream 626737a5791b 215eef4a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in jbd2_journal_commit_transaction
2024/05/04 17:33 upstream 7367539ad4b0 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in jbd2_journal_commit_transaction
2024/07/21 22:38 upstream 2c9b3512402e b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in jbd2_journal_commit_transaction
2024/07/21 14:32 upstream 2c9b3512402e b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in jbd2_journal_commit_transaction
2024/07/20 15:02 upstream 3c3ff7be9729 b88348e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in jbd2_journal_commit_transaction
2024/07/04 01:59 upstream 8a9c6c40432e 409d975c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in jbd2_journal_commit_transaction
2024/07/09 02:46 linux-next 0b58e108042b bc23a442 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in jbd2_journal_commit_transaction
2024/06/19 04:16 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing b0fc24f36191 41b7e219 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in jbd2_journal_commit_transaction
* Struck through repros no longer work on HEAD.