syzbot


INFO: task hung in __sync_dirty_buffer

Status: fixed on 2023/07/01 16:05
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+91dccab7c64e2850a4e5@syzkaller.appspotmail.com
Fix commit: f4ce24f54d9c ext4: fix deadlock when converting an inline directory in nojournal mode
First crash: 970d, last: 317d
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: INFO: task hung in __sync_dirty_buffer (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
Discussions (4)
Title Replies (including bot) Last reply
[PATCH] ext4: fix deadlock when converting an inline directory in nojournal mode 1 (1) 2023/05/07 02:16
[syzbot] Monthly ext4 report (Apr 2023) 0 (1) 2023/04/28 15:06
[syzbot] [ext4] Monthly Report 0 (1) 2023/03/24 15:59
[syzbot] INFO: task hung in __sync_dirty_buffer 0 (1) 2021/09/01 20:17
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 INFO: task hung in __sync_dirty_buffer ext4 nilfs2 C error 9 427d 1303d 0/1 upstream: reported C repro on 2020/09/29 05:34
linux-4.19 INFO: task hung in __sync_dirty_buffer ext4 nilfs2 C error 25 416d 1291d 0/1 upstream: reported C repro on 2020/10/11 09:03
linux-6.1 INFO: task hung in __sync_dirty_buffer 2 350d 374d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:07
linux-5.15 INFO: task hung in __sync_dirty_buffer 10 344d 382d 0/3 auto-obsoleted due to no activity on 2023/08/22 15:19
Last patch testing requests (1)
Created Duration User Patch Repo Result
2023/05/07 01:33 22m tytso@mit.edu git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tt/next OK log
Fix bisection attempts (4)
Created Duration User Patch Repo Result
2022/01/28 05:41 12m bisect fix upstream error job log (0)
2021/11/30 17:34 25m bisect fix upstream job log (0) log
2021/10/31 13:21 25m bisect fix upstream job log (0) log
2021/10/01 10:43 25m bisect fix upstream job log (0) log

Sample crash report:
INFO: task syz-executor362:4996 blocked for more than 143 seconds.
      Not tainted 6.3.0-syzkaller-12423-g865fdb08197e #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor362 state:D stack:22656 pid:4996  ppid:4995   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0x187b/0x4900 kernel/sched/core.c:6669
 schedule+0xc3/0x180 kernel/sched/core.c:6745
 io_schedule+0x8c/0x100 kernel/sched/core.c:8979
 bit_wait_io+0x12/0xc0 kernel/sched/wait_bit.c:209
 __wait_on_bit_lock+0xbd/0x1a0 kernel/sched/wait_bit.c:90
 out_of_line_wait_on_bit_lock+0x1d4/0x250 kernel/sched/wait_bit.c:117
 wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
 __lock_buffer fs/buffer.c:70 [inline]
 lock_buffer include/linux/buffer_head.h:406 [inline]
 __sync_dirty_buffer+0x120/0x380 fs/buffer.c:2807
 __ext4_handle_dirty_metadata+0x2a6/0x820 fs/ext4/ext4_jbd2.c:387
 ext4_handle_dirty_dirblock+0x362/0x6f0 fs/ext4/namei.c:438
 ext4_finish_convert_inline_dir+0x57b/0x6f0 fs/ext4/inline.c:1178
 ext4_convert_inline_data_nolock+0xa01/0xd80 fs/ext4/inline.c:1255
 ext4_try_add_inline_entry+0x809/0xb70 fs/ext4/inline.c:1328
 ext4_add_entry+0x535/0x1010 fs/ext4/namei.c:2384
 ext4_add_nondir+0x98/0x290 fs/ext4/namei.c:2771
 ext4_create+0x376/0x550 fs/ext4/namei.c:2816
 lookup_open fs/namei.c:3492 [inline]
 open_last_lookups fs/namei.c:3560 [inline]
 path_openat+0x13df/0x3170 fs/namei.c:3788
 do_filp_open+0x234/0x490 fs/namei.c:3818
 do_sys_openat2+0x13f/0x500 fs/open.c:1356
 do_sys_open fs/open.c:1372 [inline]
 __do_sys_openat fs/open.c:1388 [inline]
 __se_sys_openat fs/open.c:1383 [inline]
 __x64_sys_openat+0x247/0x290 fs/open.c:1383
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6279d15279
RSP: 002b:00007fffe9b67c08 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f6279d15279
RDX: 000000000000275a RSI: 0000000020000100 RDI: 00000000ffffff9c
RBP: 0000000020000100 R08: 00007f6279d83ec0 R09: 00007f6279d83ec0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffe9b67c30
R13: 0000000000000000 R14: 431bde82d7b634db R15: 0000000000000000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8cf277b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8cf27b70 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by khungtaskd/28:
 #0: ffffffff8cf275e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by klogd/4436:
 #0: ffff8880b993c1d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:558
2 locks held by getty/4747:
 #0: ffff88802d81a098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015802f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6ab/0x1db0 drivers/tty/n_tty.c:2176
3 locks held by syz-executor362/4996:
 #0: ffff88807c4ba460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:394
 #1: ffff88807827f200 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #1: ffff88807827f200 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: open_last_lookups fs/namei.c:3557 [inline]
 #1: ffff88807827f200 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: path_openat+0x7ba/0x3170 fs/namei.c:3788
 #2: ffff88807827eec8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
 #2: ffff88807827eec8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_add_inline_entry+0xf6/0xb70 fs/ext4/inline.c:1286

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.3.0-syzkaller-12423-g865fdb08197e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x498/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x187/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xec2/0xf00 kernel/hung_task.c:379
 kthread+0x2b8/0x350 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 41 Comm: kworker/u4:2 Not tainted 6.3.0-syzkaller-12423-g865fdb08197e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:__mutex_unlock_slowpath+0x735/0x750 kernel/locking/mutex.c:952
Code: 05 00 00 00 00 00 41 c7 44 05 0a 00 00 00 00 66 41 c7 44 05 0e 00 00 65 48 8b 04 25 28 00 00 00 48 3b 84 24 c0 00 00 00 75 0f <48> 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 b7 0e f7 ff 0f 1f
RSP: 0018:ffffc90000b279a0 EFLAGS: 00000246
RAX: 03569676234bc300 RBX: 0000000000000000 RCX: ffffffff8ab7cb3c
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffc90000b27a40
RBP: ffffc90000b27ab0 R08: dffffc0000000000 R09: fffff52000164f49
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffffffff2364230
R13: dffffc0000000000 R14: ffffffff8cdd8980 R15: 1ffff92000164f48
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000560dc8964680 CR3: 000000000cd30000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 arch_jump_label_transform_queue+0x81/0xd0 arch/x86/kernel/jump_label.c:139
 __jump_label_update+0x177/0x3a0 kernel/jump_label.c:475
 static_key_disable_cpuslocked+0xce/0x1b0 kernel/jump_label.c:235
 static_key_disable+0x1a/0x20 kernel/jump_label.c:243
 toggle_allocation_gate+0x1b8/0x250 mm/kfence/core.c:836
 process_one_work+0x8a0/0x10e0 kernel/workqueue.c:2405
 worker_thread+0xa63/0x1210 kernel/workqueue.c:2552
 kthread+0x2b8/0x350 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Crashes (832):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/05/03 02:43 upstream 865fdb08197e 48e0a81d .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in __sync_dirty_buffer
2023/03/31 16:09 upstream 62bad54b26db f325deb0 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/03/25 02:38 upstream 1e760fa3596e 9700afae .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in __sync_dirty_buffer
2023/03/20 16:56 upstream e8d018dd0257 7939252e .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/03/16 17:08 upstream 9c1bec9c0b08 18b58603 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/02/20 13:49 upstream c9c3395d5e3d bcdf85f8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/02/19 19:28 upstream 925cf0457d7e bcdf85f8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/01/27 13:07 upstream 7c46948a6e9c 9dfcf09c .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/01/21 10:25 upstream edc00350d205 cc0f9968 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/01/19 00:06 upstream c1649ec55708 4620c2d9 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/01/16 06:06 upstream 5dc4c995db9e a63719e7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/01/08 14:59 upstream 9b43a525db12 1dac8c7a .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/01/07 04:15 upstream 1f5abbd77e2c 1dac8c7a .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2022/12/27 01:20 upstream 1b929c02afd3 9da18ae8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2022/12/26 12:26 upstream 1b929c02afd3 9da18ae8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2022/12/25 07:33 upstream 72a85e2b0a1e 9da18ae8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2022/12/21 09:19 upstream 6feb57c2fd7c d3e76707 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2022/12/13 13:14 upstream 3a28c2c89f4b 67be1ae7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2022/12/10 14:09 upstream 3ecc37918c80 67be1ae7 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2022/12/08 11:20 upstream 479174d402bc d88f3abb .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2022/11/28 08:23 upstream cf562a45a0d5 f4470a7b .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2021/12/29 05:03 upstream ecf71de775a0 76c8cf06 .config console log report syz C ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2021/08/28 20:15 upstream 64b4fc45bea6 be2c130d .config console log report syz C ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/04 07:12 linux-next 92e815cf07ed b5918830 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/03/05 07:44 linux-next 1acf39ef8f14 f8902b57 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/02/24 12:05 linux-next 0222aa9800b2 9e2ebb3c .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/02/19 17:10 linux-next c068f40300a0 bcdf85f8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/01/27 04:28 linux-next 691781f561e9 9dfcf09c .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/01/21 23:10 linux-next d514392f17fd 559a440a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/01/07 08:16 linux-next cc3c08b41a9c 1dac8c7a .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/01/21 04:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci de8041bf6ca8 559a440a .config console log report syz C [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2023/01/18 23:55 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 42660d9e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2023/01/15 19:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 a63719e7 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2023/01/13 09:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 96166539 .config console log report syz C [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2023/01/10 06:22 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 358a161a6a9e 1dac8c7a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2023/01/07 04:49 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ae87308093bc 1dac8c7a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2022/12/19 23:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a5541c0811a0 c52b2efb .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2022/12/11 21:12 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a5541c0811a0 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2022/12/08 16:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a5541c0811a0 1034e5fa .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2022/12/02 07:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci cdb931b58ff5 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2022/12/01 10:25 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci cdb931b58ff5 4c2a66e8 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2022/11/27 14:58 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6d464646530f 74a66371 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2023/05/07 23:41 linux-next 83e5775d7afd 90c93c40 .config strace log report syz [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/14 01:37 upstream d4d58949a6ea 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/13 17:02 upstream 9a48d6046722 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/13 12:56 upstream 9a48d6046722 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/13 05:42 upstream 9a48d6046722 ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/13 00:00 upstream cc3c44c9fda2 ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/12 22:00 upstream cc3c44c9fda2 ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/12 17:33 upstream cc3c44c9fda2 ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/12 09:18 upstream 105131df9c3b adb9a3cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/12 03:40 upstream 105131df9c3b adb9a3cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/12 01:51 upstream 105131df9c3b adb9a3cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/11 21:37 upstream 105131df9c3b adb9a3cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/11 18:49 upstream 105131df9c3b adb9a3cd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/11 13:55 upstream d295b66a7b66 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/11 09:39 upstream d295b66a7b66 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/10 20:24 upstream 16a8829130ca 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/09 14:34 upstream ba0ad6ed89fd 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/09 12:46 upstream ba0ad6ed89fd 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/09 05:09 upstream ba0ad6ed89fd c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/09 03:03 upstream ba0ad6ed89fd c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/09 00:53 upstream ba0ad6ed89fd c7a5e2a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/08 08:09 upstream 17784de648be 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/08 05:42 upstream 17784de648be 90c93c40 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/07 21:22 upstream 17784de648be 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/07 16:49 upstream fc4354c6e5c2 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/07 13:15 upstream fc4354c6e5c2 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/06 16:29 upstream 2e1e1337881b 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/06 07:01 upstream 7163a2111f6c de870ca5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/05 06:46 upstream 78b421b6a7c6 518a39a6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/05 00:52 upstream 1a5304fecee5 518a39a6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/04 01:25 upstream 89b7fd5d7f3c b5918830 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/04 00:05 upstream 348551ddaf31 b5918830 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/03 20:56 upstream 348551ddaf31 b5918830 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/03 19:35 upstream 348551ddaf31 b5918830 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/03 08:37 upstream 7df047b3f0aa 48e0a81d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/03 07:08 upstream 7df047b3f0aa 48e0a81d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/02 15:31 upstream 865fdb08197e 52d40fd2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/02 09:54 upstream c8c655c34e33 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __sync_dirty_buffer
2023/05/02 05:19 upstream c8c655c34e33 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/01 13:49 upstream 58390c8ce1bd 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/01 08:42 upstream 58390c8ce1bd 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/01 06:12 upstream 58390c8ce1bd 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/05/01 04:53 upstream 58390c8ce1bd 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __sync_dirty_buffer
2023/04/02 11:12 upstream 00c7b5f4ddc5 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __sync_dirty_buffer
2023/05/09 21:07 linux-next 52025ebbb518 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/07 09:03 linux-next 83e5775d7afd 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/05/07 03:26 linux-next 83e5775d7afd 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __sync_dirty_buffer
2023/06/12 05:30 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 99a670b2069c 49519f06 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 INFO: task hung in __sync_dirty_buffer
2023/04/30 06:50 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 62df2017 .config console log report info ci-qemu2-riscv64 INFO: task hung in __sync_dirty_buffer
2023/02/18 22:56 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2d3827b3f393 bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __sync_dirty_buffer
2022/04/15 03:46 linux-next 40354149f4d7 b17b2923 .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task can't die in bit_wait_io
* Struck through repros no longer work on HEAD.