syzbot


INFO: task hung in lock_extent

Status: upstream: reported C repro on 2023/01/28 07:38
Subsystems: btrfs (incorrect?)
Reported-by: syzbot+eaa05fbc7563874b7ad2@syzkaller.appspotmail.com
First crash: 96d, last: 1d03h

Cause bisection: failed (error log, bisect log)

Sample crash report:
INFO: task kworker/u4:0:5172 blocked for more than 143 seconds.
      Not tainted 6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:0    state:D stack:22528 pid:5172  ppid:2      flags:0x00004000
Workqueue: btrfs-endio-write btrfs_work_helper
Call Trace:
 <TASK>
 __schedule+0x13ca/0x43c0
 schedule+0xc3/0x190
 wait_extent_bit+0x50c/0x6a0
 lock_extent+0x1bb/0x270
 btrfs_finish_ordered_io+0x5de/0x1c50
 btrfs_work_helper+0x43a/0xe90
 process_one_work+0x96c/0x13e0
 worker_thread+0xa63/0x1210
 kthread+0x270/0x300
 ret_from_fork+0x1f/0x30
 </TASK>
INFO: task kworker/u4:1:5243 blocked for more than 143 seconds.
      Not tainted 6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:1    state:D stack:24000 pid:5243  ppid:2      flags:0x00004000
Workqueue: btrfs-endio-write btrfs_work_helper
Call Trace:
 <TASK>
 __schedule+0x13ca/0x43c0
 schedule+0xc3/0x190
 wait_extent_bit+0x50c/0x6a0
 lock_extent+0x1bb/0x270
 btrfs_finish_ordered_io+0x5de/0x1c50
 btrfs_work_helper+0x43a/0xe90
 process_one_work+0x96c/0x13e0
 worker_thread+0xa63/0x1210
 kthread+0x270/0x300
 ret_from_fork+0x1f/0x30
 </TASK>
INFO: task syz-executor359:8085 blocked for more than 143 seconds.
      Not tainted 6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor359 state:D stack:23784 pid:8085  ppid:5118   flags:0x00004004
Call Trace:
 <TASK>
 __schedule+0x13ca/0x43c0
 schedule+0xc3/0x190
 btrfs_start_ordered_extent+0x4cd/0x760
 btrfs_wait_ordered_range+0x152/0x260
 btrfs_sync_file+0x5f8/0x1220
 btrfs_do_write_iter+0xccc/0x1270
 vfs_write+0x7dd/0xc50
 ksys_write+0x17c/0x2a0
 do_syscall_64+0x41/0xc0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7443d406c9
RSP: 002b:00007f7443ce3208 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f7443dc2788 RCX: 00007f7443d406c9
RDX: 0000000000000128 RSI: 0000000020004400 RDI: 0000000000000006
RBP: 00007f7443dc2780 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f7443dc278c
R13: 00007ffe553b460f R14: 00007f7443ce3300 R15: 0000000000022000
 </TASK>
INFO: task syz-executor359:8103 blocked for more than 144 seconds.
      Not tainted 6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor359 state:D stack:24968 pid:8103  ppid:5118   flags:0x00004004
Call Trace:
 <TASK>
 __schedule+0x13ca/0x43c0
 schedule+0xc3/0x190
 rwsem_down_read_slowpath+0x5ef/0x930
 __down_read_common+0x54/0x290
 btrfs_page_mkwrite+0x416/0xc90
 do_page_mkwrite+0x1a1/0x600
 do_wp_page+0x506/0x3270
 handle_mm_fault+0x2388/0x51c0
 exc_page_fault+0x66a/0x880
 asm_exc_page_fault+0x26/0x30
RIP: 0010:copy_user_short_string+0xd/0x40
Code: 74 0a 89 d1 f3 a4 89 c8 0f 01 ca c3 89 d0 0f 01 ca c3 01 ca eb e7 0f 1f 80 00 00 00 00 89 d1 83 e2 07 c1 e9 03 74 12 4c 8b 06 <4c> 89 07 48 8d 76 08 48 8d 7f 08 ff c9 75 ee 21 d2 74 10 89 d1 8a
RSP: 0018:ffffc90005df7330 EFLAGS: 00050202
RAX: ffffffff8435f301 RBX: 00007fffffffefc8 RCX: 0000000000000007
RDX: 0000000000000000 RSI: ffffc90005df73e0 RDI: 0000000020000120
RBP: ffffc90005df7488 R08: 0000000000000000 R09: fffff52000bbee83
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000038
R13: ffffc90005df73e0 R14: 0000000020000120 R15: ffffc90005df73e0
 _copy_to_user+0xed/0x130
 fiemap_fill_next_extent+0x235/0x410
 emit_fiemap_extent+0x242/0x3f0
 fiemap_process_hole+0x32c/0xb40
 extent_fiemap+0xe42/0x2100
 btrfs_fiemap+0x178/0x1e0
 do_vfs_ioctl+0x194f/0x2a40
 __se_sys_ioctl+0x81/0x160
 do_syscall_64+0x41/0xc0
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7443d406c9
RSP: 002b:00007f743c8c2208 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7443dc2798 RCX: 00007f7443d406c9
RDX: 0000000020000100 RSI: 00000000c020660b RDI: 0000000000000005
RBP: 00007f7443dc2790 R08: 00007f743c8c2700 R09: 0000000000000000
R10: 00007f743c8c2700 R11: 0000000000000246 R12: 00007f7443dc279c
R13: 00007ffe553b460f R14: 00007f743c8c2300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8cf26e10 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xce0
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8cf27610 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xce0
1 lock held by khungtaskd/28:
 #0: ffffffff8cf26c40 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/4750:
 #0: ffff88802b963098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70
 #1: ffffc900015902f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x53b/0x1630
3 locks held by kworker/u4:0/5172:
 #0: ffff888020ce5938 ((wq_completion)btrfs-endio-write){+.+.}-{0:0}, at: process_one_work+0x7eb/0x13e0
 #1: ffffc90003e9fd20 ((work_completion)(&work->normal_work)){+.+.}-{0:0}, at: process_one_work+0x835/0x13e0
 #2: ffff88807b3de430 (btrfs_ordered_extent){++++}-{0:0}, at: btrfs_finish_ordered_io+0x33b/0x1c50
3 locks held by kworker/u4:1/5243:
 #0: ffff888020ce5938 ((wq_completion)btrfs-endio-write){+.+.}-{0:0}, at: process_one_work+0x7eb/0x13e0
 #1: ffffc90004877d20 ((work_completion)(&work->normal_work)){+.+.}-{0:0}, at: process_one_work+0x835/0x13e0
 #2: ffff88807b3de430 (btrfs_ordered_extent){++++}-{0:0}, at: btrfs_finish_ordered_io+0x33b/0x1c50
4 locks held by syz-executor359/8085:
 #0: ffff88802150f9e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x254/0x2f0
 #1: ffff888076a2a460 (sb_writers#10){.+.+}-{0:0}, at: vfs_write+0x27f/0xc50
 #2: ffff888073643600 (&sb->s_type->i_mutex_key#15){++++}-{3:3}, at: btrfs_inode_lock+0x4d/0xd0
 #3: ffff888073643488 (&ei->i_mmap_lock){++++}-{3:3}, at: btrfs_inode_lock+0xc5/0xd0
3 locks held by syz-executor359/8103:
 #0: ffff8880754b4758 (&mm->mmap_lock){++++}-{3:3}, at: exc_page_fault+0x18d/0x880
 #1: ffff888076a2a558 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x1a1/0x600
 #2: ffff888073643488 (&ei->i_mmap_lock){++++}-{3:3}, at: btrfs_page_mkwrite+0x416/0xc90

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Call Trace:
 <TASK>
 dump_stack_lvl+0x1b5/0x2a0
 nmi_cpu_backtrace+0x47b/0x500
 nmi_trigger_cpumask_backtrace+0x1d3/0x430
 watchdog+0xf70/0xfb0
 kthread+0x270/0x300
 ret_from_fork+0x1f/0x30
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 75 Comm: kworker/u4:4 Not tainted 6.2.0-rc6-syzkaller-00258-gdb27c22251e7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:lock_is_held_type+0x51/0x180
Code: b8 1e c1 03 00 0f 84 f0 00 00 00 65 8b 05 d7 99 6c 75 85 c0 0f 85 e1 00 00 00 65 4c 8b 2d 87 b9 6d 75 41 83 bd 34 0a 00 00 00 <0f> 85 cb 00 00 00 41 89 f6 49 89 ff 9c 8f 04 24 4c 8b 24 24 fa 48
RSP: 0018:ffffc90001577778 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 1ffff920002aeef8 RCX: 0000000080000001
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: ffffffff8cf26bc0
RBP: 00000000ffffffff R08: dffffc0000000000 R09: fffffbfff1cadb16
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc90001577a40
R13: ffff8880189d3a80 R14: dffffc0000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056029596d000 CR3: 000000000cc8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rcu_read_lock_sched_held+0x8b/0x110
 lock_release+0x106/0xa70
 __mutex_unlock_slowpath+0xe2/0x750
 arch_jump_label_transform_queue+0x81/0xd0
 __jump_label_update+0x177/0x3a0
 static_key_disable_cpuslocked+0xce/0x1b0
 static_key_disable+0x1a/0x20
 toggle_allocation_gate+0x1a9/0x240
 process_one_work+0x96c/0x13e0
 worker_thread+0xa63/0x1210
 kthread+0x270/0x300
 ret_from_fork+0x1f/0x30
 </TASK>

Crashes (66):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci2-upstream-fs 2023/02/05 09:24 upstream db27c22251e7 be607b78 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/24 07:24 upstream 7bf70dbb1882 9dfcf09c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/21 13:00 upstream 17214b70a159 7939252e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/19 23:15 upstream a3671bd86a97 7939252e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-kasan-gce-smack-root 2023/03/19 13:32 upstream a3671bd86a97 7939252e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-kasan-gce-root 2023/03/18 07:35 upstream 8d3c682a5e3d 7939252e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/17 22:12 upstream 38e04b3e4240 7939252e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/16 16:35 upstream 9c1bec9c0b08 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-kasan-gce-root 2023/03/16 06:17 upstream 9c1bec9c0b08 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/15 12:16 upstream 6015b1aca1a2 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/15 08:11 upstream 4979bf866825 0d5c4377 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/14 20:18 upstream 4979bf866825 0d5c4377 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/13 01:14 upstream 134231664868 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/06 05:55 upstream f915322fe014 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/04 11:29 upstream 0a3f9a6b0265 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/04 07:45 upstream 0a3f9a6b0265 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/03 22:17 upstream 2eb29d59ddf0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/03 10:47 upstream 2eb29d59ddf0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/03/02 17:40 upstream ee3f96b16468 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/24 20:44 upstream d2980d8d8265 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/13 04:42 upstream 711e9a4d52bf 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/10 23:11 upstream 38c1e0c65865 e29a17f5 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/08 15:20 upstream 0983f6bf2bfc fc9c934e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/08 08:10 upstream 513c1a3d3f19 15c3d445 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/07 17:33 upstream 05ecb680708a 5bc3be51 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/06 10:35 upstream 4ec5183ec486 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/06 01:37 upstream 4ec5183ec486 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/05 14:01 upstream 837c07cf68fe be607b78 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/05 11:08 upstream 837c07cf68fe be607b78 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/02/01 00:14 upstream 22b8077d0fce b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/31 20:24 upstream 22b8077d0fce b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/31 16:32 upstream 22b8077d0fce b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/31 02:09 upstream 6d796c50f84c b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/30 20:06 upstream 6d796c50f84c b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/30 15:17 upstream 6d796c50f84c b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-kasan-gce-smack-root 2023/01/30 07:07 upstream ab072681eabe 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/30 02:41 upstream ab072681eabe 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-kasan-gce-selinux-root 2023/01/29 19:14 upstream c96618275234 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-kasan-gce-root 2023/01/29 19:08 upstream c96618275234 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/25 20:15 upstream 948ef7bb70c4 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/25 18:38 upstream 948ef7bb70c4 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/24 22:26 upstream fb6e71db53f3 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/23 15:43 upstream 2475bf0250de 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/23 05:50 upstream 2475bf0250de cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/21 12:02 upstream edc00350d205 cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/19 20:19 upstream 081edded9b38 71197f3a .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/18 04:18 upstream 6e50979a9c87 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/18 00:53 upstream 6e50979a9c87 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/17 01:34 upstream d532dd102151 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/16 22:15 upstream d532dd102151 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/16 20:08 upstream 5dc4c995db9e a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/16 18:59 upstream 5dc4c995db9e a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/16 15:37 upstream 5dc4c995db9e a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/16 08:45 upstream 5dc4c995db9e a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/15 19:10 upstream 7c6984405241 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/14 11:09 upstream 97ec4d559d93 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2023/01/13 22:51 upstream d9fc1511728c 529798b0 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2022/12/23 16:24 upstream 8395ae05cb5a 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2022/12/20 07:31 upstream aeba12b26c79 c52b2efb .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2022/12/16 19:39 upstream 84e57d292203 05494336 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci2-upstream-fs 2022/12/15 22:54 upstream 041fae9c105a 6f9c033e .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-linux-next-kasan-gce-root 2023/02/05 05:49 linux-next 4fafd96910ad be607b78 .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-linux-next-kasan-gce-root 2023/01/29 19:24 linux-next e2f86c02fdc9 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
ci-upstream-gce-arm64 2023/02/22 21:58 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a9b06ec42c0f 409945bc .config console log report info [disk image] [vmlinux] [kernel image] INFO: task hung in lock_extent
* Struck through repros no longer work on HEAD.