syzbot


INFO: task hung in extent_writepages

Status: upstream: reported C repro on 2023/08/02 17:51
Subsystems: btrfs
[Documentation on labels]
Reported-by: syzbot+d9d40a56a26bdd36922e@syzkaller.appspotmail.com
First crash: 436d, last: 69d
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: BUG: unable to handle kernel NULL pointer dereference in btrfs_release_extent_buffer_pages (log)
Repro: C syz .config
  
Fix bisection: fixed by (bisect log) :
commit a1912f712188291f9d7d434fba155461f1ebef66
Author: Josef Bacik <josef@toxicpanda.com>
Date: Wed Nov 22 17:17:55 2023 +0000

  btrfs: remove code for inode_cache and recovery mount options

  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [btrfs?] INFO: task hung in extent_writepages 0 (2) 2024/03/12 11:12
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in extent_writepages 1 358d 358d 0/3 auto-obsoleted due to no activity on 2023/08/22 08:46
Last patch testing requests (4)
Created Duration User Patch Repo Result
2024/02/04 21:23 26m retest repro upstream OK log
2024/01/08 02:00 16m retest repro upstream OK log
2023/11/09 02:28 20m retest repro upstream report log
2023/08/25 17:21 23m retest repro upstream report log

Sample crash report:
INFO: task kworker/u4:2:30 blocked for more than 143 seconds.
      Not tainted 6.5.0-rc3-syzkaller-00275-gffabf7c73176 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:2    state:D stack:20560 pid:30    ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-btrfs-47)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 io_schedule+0x8c/0x100 kernel/sched/core.c:9028
 folio_wait_bit_common+0x86c/0x12b0 mm/filemap.c:1304
 folio_lock include/linux/pagemap.h:959 [inline]
 extent_write_cache_pages fs/btrfs/extent_io.c:2140 [inline]
 extent_writepages+0xcea/0x2d00 fs/btrfs/extent_io.c:2286
 do_writepages+0x3a6/0x670 mm/page-writeback.c:2553
 __writeback_single_inode+0x155/0xfa0 fs/fs-writeback.c:1603
 writeback_sb_inodes+0x8e3/0x11d0 fs/fs-writeback.c:1894
 __writeback_inodes_wb+0x11b/0x260 fs/fs-writeback.c:1965
 wb_writeback+0x461/0xc60 fs/fs-writeback.c:2072
 wb_check_background_flush fs/fs-writeback.c:2142 [inline]
 wb_do_writeback fs/fs-writeback.c:2230 [inline]
 wb_workfn+0xc6f/0xff0 fs/fs-writeback.c:2257
 process_one_work+0x92c/0x12c0 kernel/workqueue.c:2597
 worker_thread+0xa63/0x1210 kernel/workqueue.c:2748
 kthread+0x2b8/0x350 kernel/kthread.c:389
 ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:296
RIP: 0000:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
INFO: task kworker/u4:5:1145 blocked for more than 144 seconds.
      Not tainted 6.5.0-rc3-syzkaller-00275-gffabf7c73176 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:5    state:D stack:21608 pid:1145  ppid:2      flags:0x00004000
Workqueue: btrfs-endio-write btrfs_work_helper
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 wait_on_state fs/btrfs/extent-io-tree.c:719 [inline]
 wait_extent_bit+0x50c/0x670 fs/btrfs/extent-io-tree.c:763
 lock_extent+0x1c0/0x270 fs/btrfs/extent-io-tree.c:1755
 btrfs_finish_one_ordered+0x5bf/0x1c80 fs/btrfs/inode.c:3242
 btrfs_work_helper+0x380/0xbe0 fs/btrfs/async-thread.c:314
 process_one_work+0x92c/0x12c0 kernel/workqueue.c:2597
 worker_thread+0xa63/0x1210 kernel/workqueue.c:2748
 kthread+0x2b8/0x350 kernel/kthread.c:389
 ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:296
RIP: 0000:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
INFO: task syz-executor376:6242 blocked for more than 144 seconds.
      Not tainted 6.5.0-rc3-syzkaller-00275-gffabf7c73176 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor376 state:D stack:23592 pid:6242  ppid:5052   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 wait_on_state fs/btrfs/extent-io-tree.c:719 [inline]
 wait_extent_bit+0x50c/0x670 fs/btrfs/extent-io-tree.c:763
 lock_extent+0x1c0/0x270 fs/btrfs/extent-io-tree.c:1755
 find_lock_delalloc_range+0x4b5/0x980 fs/btrfs/extent_io.c:443
 writepage_delalloc+0x1bd/0x490 fs/btrfs/extent_io.c:1235
 __extent_writepage fs/btrfs/extent_io.c:1492 [inline]
 extent_write_cache_pages fs/btrfs/extent_io.c:2160 [inline]
 extent_writepages+0x14bd/0x2d00 fs/btrfs/extent_io.c:2286
 do_writepages+0x3a6/0x670 mm/page-writeback.c:2553
 filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:393
 __filemap_fdatawrite_range mm/filemap.c:426 [inline]
 filemap_fdatawrite_range+0x16e/0x1e0 mm/filemap.c:444
 btrfs_fdatawrite_range fs/btrfs/file.c:3850 [inline]
 start_ordered_ops fs/btrfs/file.c:1725 [inline]
 btrfs_sync_file+0x424/0x1330 fs/btrfs/file.c:1800
 generic_write_sync include/linux/fs.h:2493 [inline]
 btrfs_do_write_iter+0xb45/0x1020 fs/btrfs/file.c:1677
 call_write_iter include/linux/fs.h:1871 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x782/0xaf0 fs/read_write.c:584
 ksys_write+0x1a0/0x2c0 fs/read_write.c:637
 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:0x7f0fa348afc9
RSP: 002b:00007f0fa3447218 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f0fa35176c8 RCX: 00007f0fa348afc9
RDX: 0000000000000128 RSI: 0000000020004400 RDI: 0000000000000006
RBP: 00007f0fa35176c0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f0fa34e41b0
R13: 61635f65646f6e69 R14: 65646f7475616f6e R15: 7261637369646f6e
 </TASK>
INFO: task syz-executor376:6283 blocked for more than 145 seconds.
      Not tainted 6.5.0-rc3-syzkaller-00275-gffabf7c73176 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor376 state:D stack:21704 pid:6283  ppid:5052   flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5381 [inline]
 __schedule+0x1873/0x48f0 kernel/sched/core.c:6710
 schedule+0xc3/0x180 kernel/sched/core.c:6786
 wait_on_state fs/btrfs/extent-io-tree.c:719 [inline]
 wait_extent_bit+0x50c/0x670 fs/btrfs/extent-io-tree.c:763
 lock_extent+0x1c0/0x270 fs/btrfs/extent-io-tree.c:1755
 btrfs_page_mkwrite+0x5bd/0xd10 fs/btrfs/inode.c:8271
 do_page_mkwrite+0x1a4/0x600 mm/memory.c:2942
 wp_page_shared mm/memory.c:3294 [inline]
 do_wp_page+0x559/0x3a70 mm/memory.c:3376
 handle_pte_fault mm/memory.c:4955 [inline]
 __handle_mm_fault mm/memory.c:5079 [inline]
 handle_mm_fault+0x1c58/0x5410 mm/memory.c:5233
 do_user_addr_fault arch/x86/mm/fault.c:1392 [inline]
 handle_page_fault arch/x86/mm/fault.c:1486 [inline]
 exc_page_fault+0x266/0x7c0 arch/x86/mm/fault.c:1542
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0010:rep_movs_alternative+0x33/0xb0 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 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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: 0000:ffffc9000b76f330 EFLAGS: 00050206
RAX: 0000000000000000 RBX: 0000000020000158 RCX: 0000000000000038
RDX: 0000000000000000 RSI: ffffc9000b76f3e0 RDI: 0000000020000120
RBP: ffffc9000b76f498 R08: ffffc9000b76f417 R09: 1ffff920016ede82
R10: dffffc0000000000 R11: fffff520016ede83 R12: 0000000000000038
R13: ffffc9000b76f3e0 R14: 0000000020000120 R15: ffffc9000b76f3e0
 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/0xa0 lib/usercopy.c:41
 copy_to_user include/linux/uaccess.h:191 [inline]
 fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:144
 emit_fiemap_extent+0x256/0x410 fs/btrfs/extent_io.c:2532
 fiemap_process_hole+0x374/0xaf0 fs/btrfs/extent_io.c:2743
 extent_fiemap+0xeae/0x1fe0
 btrfs_fiemap+0x178/0x1e0 fs/btrfs/inode.c:7943
 ioctl_fiemap fs/ioctl.c:219 [inline]
 do_vfs_ioctl+0x19db/0x2b30 fs/ioctl.c:810
 __do_sys_ioctl fs/ioctl.c:868 [inline]
 __se_sys_ioctl+0x81/0x170 fs/ioctl.c:856
 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:0x7f0fa348afc9
RSP: 002b:00007f0f9c026218 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f0fa35176d8 RCX: 00007f0fa348afc9
RDX: 0000000020000100 RSI: 00000000c020660b RDI: 0000000000000005
RBP: 00007f0fa35176d0 R08: 00007ffc74220257 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f0fa34e41b0
R13: 61635f65646f6e69 R14: 65646f7475616f6e R15: 7261637369646f6e
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8d328db0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:522
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8d329170 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:522
1 lock held by khungtaskd/28:
 #0: ffffffff8d328be0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:2/30:
 #0: ffff88814267e938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7e3/0x12c0 kernel/workqueue.c:2569
 #1: ffffc90000a6fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x82b/0x12c0 kernel/workqueue.c:2571
 #2: ffff88807a5d00e0 (&type->s_umount_key#43){++++}-{3:3}, at: trylock_super+0x1f/0xf0 fs/super.c:413
3 locks held by kworker/u4:5/1145:
 #0: ffff8880285ae138 ((wq_completion)btrfs-endio-write){+.+.}-{0:0}, at: process_one_work+0x7e3/0x12c0 kernel/workqueue.c:2569
 #1: ffffc9000514fd00 ((work_completion)(&work->normal_work)){+.+.}-{0:0}, at: process_one_work+0x82b/0x12c0 kernel/workqueue.c:2571
 #2: ffff888023a0a488 (btrfs_ordered_extent){++++}-{0:0}, at: btrfs_finish_one_ordered+0x343/0x1c80 fs/btrfs/inode.c:3201
2 locks held by getty/4768:
 #0: ffff88802df81098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015b02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6b1/0x1dc0 drivers/tty/n_tty.c:2187
2 locks held by syz-executor376/6242:
 #0: ffff8880201da0c8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x20f/0x2a0 fs/file.c:1046
 #1: ffff88807a5d0410 (sb_writers#9){.+.+}-{0:0}, at: vfs_write+0x216/0xaf0 fs/read_write.c:580
4 locks held by syz-executor376/6283:
 #0: ffff8880753d62b0 (&sb->s_type->i_mutex_key#14){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:781 [inline]
 #0: ffff8880753d62b0 (&sb->s_type->i_mutex_key#14){++++}-{3:3}, at: btrfs_inode_lock+0x60/0xd0 fs/btrfs/inode.c:369
 #1: ffff88807d6027a0 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:167 [inline]
 #1: ffff88807d6027a0 (&mm->mmap_lock){++++}-{3:3}, at: get_mmap_lock_carefully mm/memory.c:5261 [inline]
 #1: ffff88807d6027a0 (&mm->mmap_lock){++++}-{3:3}, at: lock_mm_and_find_vma+0x32/0x2f0 mm/memory.c:5323
 #2: ffff88807a5d0508 (sb_pagefaults){.+.+}-{0:0}, at: do_page_mkwrite+0x1a4/0x600 mm/memory.c:2942
 #3: ffff8880753d6138 (&ei->i_mmap_lock){++++}-{3:3}, at: btrfs_page_mkwrite+0x49c/0xd10 fs/btrfs/inode.c:8260

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.5.0-rc3-syzkaller-00275-gffabf7c73176 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/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:160 [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:389
 ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:296
RIP: 0000:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5903 Comm: kworker/u4:0 Not tainted 6.5.0-rc3-syzkaller-00275-gffabf7c73176 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:19 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:67 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:127 [inline]
RIP: 0010:smp_call_function_many_cond+0x1660/0x27d0 kernel/smp.c:827
Code: 85 f6 75 07 e8 31 16 0b 00 eb 0a e8 2a 16 0b 00 e8 75 d5 11 00 4c 89 fb 48 c1 eb 03 48 b8 00 00 00 00 00 fc ff df 80 3c 03 00 <74> 08 4c 89 ff e8 36 df 63 00 48 c7 84 24 60 01 00 00 00 00 00 00
RSP: 0018:ffffc9000ad9f780 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 1ffff920015b3f1c RCX: ffffffff816c3cea
RDX: dffffc0000000000 RSI: ffffffff8b0a90c0 RDI: ffffffff8b58a600
RBP: ffffc9000ad9f980 R08: ffffffff907b1307 R09: 1ffffffff20f6260
R10: dffffc0000000000 R11: fffffbfff20f6261 R12: ffff8880b993d0c0
R13: 0000000000000000 R14: 0000000000000200 R15: ffffc9000ad9f8e0
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0f9bf29000 CR3: 000000000d130000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 on_each_cpu_cond_mask+0x3f/0x80 kernel/smp.c:1003
 on_each_cpu include/linux/smp.h:71 [inline]
 text_poke_sync arch/x86/kernel/alternative.c:2001 [inline]
 text_poke_bp_batch+0x615/0x960 arch/x86/kernel/alternative.c:2273
 text_poke_flush arch/x86/kernel/alternative.c:2402 [inline]
 text_poke_finish+0x1a/0x30 arch/x86/kernel/alternative.c:2409
 arch_jump_label_transform_apply+0x17/0x30 arch/x86/kernel/jump_label.c:146
 static_key_enable_cpuslocked+0x132/0x250 kernel/jump_label.c:205
 static_key_enable+0x1a/0x20 kernel/jump_label.c:218
 toggle_allocation_gate+0xb5/0x250 mm/kfence/core.c:831
 process_one_work+0x92c/0x12c0 kernel/workqueue.c:2597
 worker_thread+0xa63/0x1210 kernel/workqueue.c:2748
 kthread+0x2b8/0x350 kernel/kthread.c:389
 ret_from_fork+0x2e/0x60 arch/x86/kernel/process.c:145
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:296
RIP: 0000:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.240 msecs

Crashes (30):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/07/29 17:34 upstream ffabf7c73176 92476829 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in extent_writepages
2023/12/25 01:57 upstream 861deac3b092 fb427a07 .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in extent_writepages
2024/02/07 02:52 upstream 99bd3cb0d12e 6404acf9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in extent_writepages
2024/01/21 19:40 upstream 7a396820222d 9bd8dcda .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2024/01/13 04:15 upstream 70d201a40823 551587c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2024/01/10 20:22 upstream ab27740f7665 04815ef1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/12/17 23:37 upstream 0e389834672c 3222d10c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/12/10 00:23 upstream b10a3ccaf6e3 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/12/09 19:13 upstream f2e8a57ee903 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/11/27 13:53 upstream 2cc14f52aeb7 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/10/26 02:07 upstream 611da07b89fd 72e794c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/10/10 14:34 upstream 94f6f0550c62 c9be5398 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/10/06 04:09 upstream 3006adf3be79 db17ad9f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/09/27 16:44 upstream 0e945134b680 2895a507 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/09/25 07:16 upstream 6465e260f487 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/05/04 20:02 upstream 1a5304fecee5 3a560463 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in extent_writepages
2023/05/01 16:35 upstream 58390c8ce1bd 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/29 05:42 upstream 33afd4b76393 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/26 00:21 upstream 173ea743bf7a 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/21 19:49 upstream 2af3e53a4dc0 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/12 00:17 upstream e62252bc55b6 49faf98d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/10 20:08 upstream 09a9639e56c0 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/10 18:13 upstream 09a9639e56c0 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/02 16:56 upstream 00c7b5f4ddc5 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/04/02 15:44 upstream 00c7b5f4ddc5 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/03/06 07:30 upstream f915322fe014 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/02/06 13:51 upstream d2d11f342b17 0a9c11b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/02/05 05:35 upstream db27c22251e7 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in extent_writepages
2023/11/26 23:16 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in extent_writepages
2023/11/19 09:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in extent_writepages
* Struck through repros no longer work on HEAD.