syzbot


INFO: task hung in btrfs_page_mkwrite

Status: upstream: reported on 2023/10/04 01:20
Subsystems: btrfs
[Documentation on labels]
Reported-by: syzbot+bdcacd75b712b0147ca7@syzkaller.appspotmail.com
First crash: 514d, last: 67d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [btrfs?] INFO: task hung in btrfs_page_mkwrite 0 (1) 2023/10/04 01:20
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in btrfs_page_mkwrite 1 314d 314d 0/3 auto-obsoleted due to no activity on 2023/09/26 02:15

Sample crash report:
INFO: task syz-executor.1:9846 blocked for more than 143 seconds.
      Not tainted 6.8.0-rc5-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:25112 pid:9846  tgid:9846  ppid:5090   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5400 [inline]
 __schedule+0x177f/0x49a0 kernel/sched/core.c:6727
 __schedule_loop kernel/sched/core.c:6802 [inline]
 schedule+0x149/0x260 kernel/sched/core.c:6817
 io_schedule+0x8c/0x110 kernel/sched/core.c:9023
 folio_wait_bit_common+0x881/0x12b0 mm/filemap.c:1274
 btrfs_page_mkwrite+0x60d/0x10c0 fs/btrfs/inode.c:8185
 do_page_mkwrite+0x19b/0x480 mm/memory.c:2966
 wp_page_shared mm/memory.c:3353 [inline]
 do_wp_page+0x20e3/0x4c90 mm/memory.c:3493
 handle_pte_fault mm/memory.c:5160 [inline]
 __handle_mm_fault+0x26ad/0x72d0 mm/memory.c:5285
 handle_mm_fault+0x27e/0x770 mm/memory.c:5450
 do_user_addr_fault arch/x86/mm/fault.c:1364 [inline]
 handle_page_fault arch/x86/mm/fault.c:1507 [inline]
 exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1563
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7f09e1c2c493
RSP: 002b:00007ffd0dacf1b0 EFLAGS: 00010246
RAX: 0000000020000600 RBX: 0000000000000008 RCX: 0000000000000000
RDX: 0000000020001440 RSI: 0000000000000000 RDI: 000055555639c360
RBP: 0000000000000008 R08: 0000000000000000 R09: 0000000000000000
R10: 000000008135d6f5 R11: 0000000000000246 R12: 00007f09e1807278
R13: fffffffffffffffe R14: 00007f09e1800000 R15: 00007f09e1807280
 </TASK>
INFO: task syz-executor.1:9847 blocked for more than 144 seconds.
      Not tainted 6.8.0-rc5-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:22968 pid:9847  tgid:9846  ppid:5090   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5400 [inline]
 __schedule+0x177f/0x49a0 kernel/sched/core.c:6727
 __schedule_loop kernel/sched/core.c:6802 [inline]
 schedule+0x149/0x260 kernel/sched/core.c:6817
 wait_extent_bit fs/btrfs/extent-io-tree.c:822 [inline]
 lock_extent+0x69d/0x860 fs/btrfs/extent-io-tree.c:1868
 btrfs_page_mkwrite+0x743/0x10c0 fs/btrfs/inode.c:8195
 do_page_mkwrite+0x19b/0x480 mm/memory.c:2966
 wp_page_shared mm/memory.c:3353 [inline]
 do_wp_page+0x20e3/0x4c90 mm/memory.c:3493
 handle_pte_fault mm/memory.c:5160 [inline]
 __handle_mm_fault+0x26ad/0x72d0 mm/memory.c:5285
 handle_mm_fault+0x27e/0x770 mm/memory.c:5450
 do_user_addr_fault arch/x86/mm/fault.c:1415 [inline]
 handle_page_fault arch/x86/mm/fault.c:1507 [inline]
 exc_page_fault+0x2ad/0x870 arch/x86/mm/fault.c:1563
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0010:rep_movs_alternative+0x33/0x70 arch/x86/lib/copy_user_64.S:58
Code: 40 83 f9 08 73 21 85 c9 74 0f 8a 06 88 07 48 ff c7 48 ff c6 48 ff c9 75 f1 c3 cc cc cc cc 66 0f 1f 84 00 00 00 00 00 48 8b 06 <48> 89 07 48 83 c6 08 48 83 c7 08 83 e9 08 74 df 83 f9 08 73 e8 eb
RSP: 0018:ffffc900033bf530 EFLAGS: 00050206
RAX: 0000000000000000 RBX: 00000000200007d8 RCX: 0000000000000038
RDX: 0000000000000000 RSI: ffffc900033bf5e0 RDI: 00000000200007a0
RBP: ffffc900033bf690 R08: ffffc900033bf617 R09: 1ffff92000677ec2
R10: dffffc0000000000 R11: fffff52000677ec3 R12: 0000000000000038
R13: ffffc900033bf5e0 R14: 00000000200007a0 R15: ffffc900033bf5e0
 copy_user_generic arch/x86/include/asm/uaccess_64.h:112 [inline]
 raw_copy_to_user arch/x86/include/asm/uaccess_64.h:133 [inline]
 _copy_to_user+0x86/0xb0 lib/usercopy.c:41
 copy_to_user include/linux/uaccess.h:191 [inline]
 fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145
 emit_last_fiemap_cache fs/btrfs/extent_io.c:2555 [inline]
 extent_fiemap+0x1b9c/0x1fe0 fs/btrfs/extent_io.c:3082
 btrfs_fiemap+0x178/0x1f0 fs/btrfs/inode.c:7863
 ioctl_fiemap fs/ioctl.c:220 [inline]
 do_vfs_ioctl+0x1a02/0x2b60 fs/ioctl.c:811
 __do_sys_ioctl fs/ioctl.c:869 [inline]
 __se_sys_ioctl+0x81/0x170 fs/ioctl.c:857
 do_syscall_64+0xf9/0x240
 entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7f09e1c7dda9
RSP: 002b:00007f09e29940c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f09e1dabf80 RCX: 00007f09e1c7dda9
RDX: 0000000020000780 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f09e1cca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f09e1dabf80 R15: 00007ffd0dacf108
 </TASK>
INFO: task syz-executor.1:9908 blocked for more than 145 seconds.
      Not tainted 6.8.0-rc5-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:27376 pid:9908  tgid:9846  ppid:5090   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5400 [inline]
 __schedule+0x177f/0x49a0 kernel/sched/core.c:6727
 __schedule_loop kernel/sched/core.c:6802 [inline]
 schedule+0x149/0x260 kernel/sched/core.c:6817
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6874
 rwsem_down_write_slowpath+0xeea/0x13b0 kernel/locking/rwsem.c:1178
 __down_write_common+0x1ae/0x200 kernel/locking/rwsem.c:1306
 inode_lock include/linux/fs.h:802 [inline]
 btrfs_inode_lock+0x4d/0xe0 fs/btrfs/inode.c:387
 btrfs_buffered_write+0x230/0x1380 fs/btrfs/file.c:1207
 btrfs_do_write_iter+0x2bb/0x1190 fs/btrfs/file.c:1690
 do_iter_readv_writev+0x46c/0x640
 vfs_writev+0x395/0xbb0 fs/read_write.c:971
 do_pwritev fs/read_write.c:1072 [inline]
 __do_sys_pwritev2 fs/read_write.c:1131 [inline]
 __se_sys_pwritev2+0x1ca/0x2d0 fs/read_write.c:1122
 do_syscall_64+0xf9/0x240
 entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7f09e1c7dda9
RSP: 002b:00007f09e29520c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007f09e1dac120 RCX: 00007f09e1c7dda9
RDX: 0000000000000001 RSI: 0000000020000580 RDI: 0000000000000004
RBP: 00007f09e1cca47a R08: 0000000000000000 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f09e1dac120 R15: 00007ffd0dacf108
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/u4:0/11:
1 lock held by khungtaskd/29:
 #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:298 [inline]
 #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:750 [inline]
 #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6614
4 locks held by kworker/u4:4/59:
2 locks held by kworker/u4:5/1088:
1 lock held by udevd/4510:
2 locks held by getty/4816:
 #0: ffff88802ba790a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900031332f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6b4/0x1e10 drivers/tty/n_tty.c:2201
3 locks held by syz-executor.1/9846:
 #0: ffff88802f4bcd20 (&vma->vm_lock->lock){++++}-{3:3}, at: vma_start_read include/linux/mm.h:663 [inline]
 #0: ffff88802f4bcd20 (&vma->vm_lock->lock){++++}-{3:3}, at: lock_vma_under_rcu+0x2f9/0x730 mm/memory.c:5606
 #1: ffff88807acf2518 (sb_pagefaults#5){.+.+}-{0:0}, at: do_page_mkwrite+0x19b/0x480 mm/memory.c:2966
 #2: ffff888077a5c208 (&ei->i_mmap_lock){++++}-{3:3}, at: btrfs_page_mkwrite+0x603/0x10c0 fs/btrfs/inode.c:8184
4 locks held by syz-executor.1/9847:
 #0: ffff888077a5c380 (&sb->s_type->i_mutex_key#23){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:812 [inline]
 #0: ffff888077a5c380 (&sb->s_type->i_mutex_key#23){++++}-{3:3}, at: btrfs_inode_lock+0x60/0xe0 fs/btrfs/inode.c:379
 #1: ffff88807a2860a0 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:165 [inline]
 #1: ffff88807a2860a0 (&mm->mmap_lock){++++}-{3:3}, at: get_mmap_lock_carefully mm/memory.c:5477 [inline]
 #1: ffff88807a2860a0 (&mm->mmap_lock){++++}-{3:3}, at: lock_mm_and_find_vma+0x32/0x2e0 mm/memory.c:5537
 #2: ffff88807acf2518 (sb_pagefaults#5){.+.+}-{0:0}, at: do_page_mkwrite+0x19b/0x480 mm/memory.c:2966
 #3: ffff888077a5c208 (&ei->i_mmap_lock){++++}-{3:3}, at: btrfs_page_mkwrite+0x603/0x10c0 fs/btrfs/inode.c:8184
2 locks held by syz-executor.1/9908:
 #0: ffff88807acf2420 (sb_writers#16){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2792 [inline]
 #0: ffff88807acf2420 (sb_writers#16){.+.+}-{0:0}, at: vfs_writev+0x2d9/0xbb0 fs/read_write.c:969
 #1: ffff888077a5c380 (&sb->s_type->i_mutex_key#23){++++}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline]
 #1: ffff888077a5c380 (&sb->s_type->i_mutex_key#23){++++}-{3:3}, at: btrfs_inode_lock+0x4d/0xe0 fs/btrfs/inode.c:387
3 locks held by syz-executor.1/10232:
 #0: ffff8880b943c918 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:559
 #1: ffff8880b9428988 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x441/0x770 kernel/sched/psi.c:988
 #2: ffff88801c334e28 (ptlock_ptr(ptdesc)#2){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
 #2: ffff88801c334e28 (ptlock_ptr(ptdesc)#2){+.+.}-{2:2}, at: __pte_offset_map_lock+0x1ba/0x300 mm/pgtable-generic.c:373
4 locks held by syz-executor.4/11587:
1 lock held by syz-executor.1/12306:
 #0: ffffffff8e136478 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
 #0: ffffffff8e136478 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3a3/0x890 kernel/rcu/tree_exp.h:995

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.8.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
 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:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xfaf/0xff0 kernel/hung_task.c:379
 kthread+0x2ef/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 12309 Comm: syz-executor.3 Not tainted 6.8.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:kasan_check_range+0x1b8/0x290 mm/kasan/generic.c:189
Code: 4d 01 fb 48 8d 5d 07 48 85 ed 48 0f 49 dd 48 83 e3 f8 48 29 dd 74 12 41 80 3b 00 0f 85 a6 00 00 00 49 ff c3 48 ff cd 75 ee 5b <41> 5c 41 5e 41 5f 5d c3 cc cc cc cc 40 84 ed 75 5f f7 c5 00 ff 00
RSP: 0000:ffffc9000331fd38 EFLAGS: 00000256
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff817115e4
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8f8439e8
RBP: 0000000000000000 R08: ffffffff8f8439ef R09: 1ffffffff1f0873d
R10: dffffc0000000000 R11: fffffbfff1f0873e R12: 1ffff92000663fb4
R13: dffffc0000000000 R14: dffffc0000000001 R15: fffffbfff1f0873e
FS:  00007f7580f7c6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7576d06000 CR3: 000000003668c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 instrument_atomic_read include/linux/instrumented.h:68 [inline]
 _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
 cpumask_test_cpu include/linux/cpumask.h:504 [inline]
 cpu_online include/linux/cpumask.h:1104 [inline]
 trace_lock_acquire include/trace/events/lock.h:24 [inline]
 lock_acquire+0xd4/0x530 kernel/locking/lockdep.c:5725
 rcu_lock_acquire include/linux/rcupdate.h:298 [inline]
 rcu_read_lock include/linux/rcupdate.h:750 [inline]
 vma_end_read+0x35/0x170 include/linux/mm.h:686
 do_user_addr_fault arch/x86/mm/fault.c:1366 [inline]
 handle_page_fault arch/x86/mm/fault.c:1507 [inline]
 exc_page_fault+0x4bd/0x870 arch/x86/mm/fault.c:1563
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7f7580229836
Code: f0 72 6e 48 63 cd 48 01 c1 49 39 4f 08 72 4c 8d 4d ff 85 ed 74 33 66 0f 1f 44 00 00 48 39 f0 72 1b 4d 8b 07 49 89 c1 49 29 f1 <47> 0f b6 0c 08 45 84 c9 74 08 45 88 0c 00 49 8b 47 10 48 83 c0 01
RSP: 002b:00007f7580f7b530 EFLAGS: 00010206
RAX: 0000000000506001 RBX: 00007f7580f7b5d0 RCX: 00000000000000c2
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007f7580f7b670
RBP: 0000000000000102 R08: 00007f7576800000 R09: 0000000000506000
R10: 0000000000000000 R11: 00007f7580f7b5e0 R12: 0000000000000001
R13: 00007f75802eccc0 R14: 0000000000000000 R15: 00007f7580f7b670
 </TASK>

Crashes (49):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/19 11:09 upstream b401b621758e 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/02/11 16:20 upstream 7521f258ea30 77b23aa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/30 02:36 upstream 41bccc98fb79 991a98f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/27 17:01 upstream 3a5879d495b2 cc4a4020 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/12 07:43 upstream 3e7aeb78ab01 dda5a988 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/11 02:18 upstream ab27740f7665 04815ef1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/10 04:26 upstream 35f11a3710cd b438bd66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/08 12:45 upstream 0dd3ee311255 d0304e9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/07 17:02 upstream 52b1853b080a d0304e9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/06 22:19 upstream 95c8a35f1c01 d0304e9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2024/01/05 05:03 upstream 5eff55d725a4 28c42cff .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/12/31 02:27 upstream 453f5db0619e fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/12/24 21:12 upstream 861deac3b092 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/12/20 14:20 upstream 55cb5f43689d 3ad490ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/11/05 04:26 upstream aea6bf908d73 500bfdc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/10/21 14:04 upstream 9c5d00cb7b6b 361b23dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/10/09 16:20 upstream 94f6f0550c62 3c53c7d9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/10/07 12:13 upstream 82714078aee4 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/10/02 10:02 upstream e81a2dabc3f3 8e26a358 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/09/30 01:12 upstream 71e58659bfc0 8e26a358 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/09/13 17:00 upstream 3669558bdf35 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/08/08 19:05 upstream 14f9643dc90a 9552ae77 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/05/29 10:20 upstream 7877cb91f108 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/05/26 17:19 upstream 9db898594c54 b40ef614 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/05/13 16:24 upstream 9a48d6046722 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/05/11 05:59 upstream d295b66a7b66 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/05/09 15:15 upstream ba0ad6ed89fd 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/05/04 17:05 upstream 1a5304fecee5 518a39a6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/25 16:51 upstream 173ea743bf7a 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/25 08:48 upstream 1a0beef98b58 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/24 18:53 upstream 457391b03803 fdc18293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/18 04:11 upstream 6a8f57ae2eb0 436577a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/15 07:25 upstream 95abc817ab3a ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/10 19:47 upstream 09a9639e56c0 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/05 14:06 upstream 76f598ba7d8e 831373d3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/04/03 14:29 upstream 7e364e56293b 41147e3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/03/31 17:27 upstream 62bad54b26db f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/03/30 07:15 upstream ffe78bbd5121 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/03/25 01:02 upstream 1e760fa3596e 9700afae .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/03/14 07:53 upstream fc89d7fb499b 026e2200 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/02/04 12:08 upstream 0136d86b7852 1b2f701a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/01/30 01:25 upstream ab072681eabe 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/01/18 21:57 upstream c1649ec55708 4620c2d9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/01/13 12:32 upstream c757fc92a3f7 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2022/12/27 23:28 upstream 1b929c02afd3 44712fbc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2022/12/23 23:26 upstream 51094a24b85e 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2022/12/10 09:27 upstream 3ecc37918c80 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2022/11/29 22:04 upstream ca57f02295f1 579a3740 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in btrfs_page_mkwrite
2023/05/08 11:11 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 14f8db1c0f9a 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in btrfs_page_mkwrite
* Struck through repros no longer work on HEAD.