syzbot


INFO: task hung in invalidate_inode_pages2_range (3)

Status: upstream: reported C repro on 2025/02/28 07:59
Subsystems: bcachefs
[Documentation on labels]
Reported-by: syzbot+de1434c5355cc909b734@syzkaller.appspotmail.com
Fix commit: bcachefs: Fix readahead involved deadlock
Patched on: [ci-upstream-linux-next-kasan-gce-root ci-upstream-rust-kasan-gce], missing on: [ci-qemu-gce-upstream-auto ci-qemu-native-arm64-kvm ci-qemu-upstream ci-qemu-upstream-386 ci-qemu2-arm32 ci-qemu2-arm64 ci-qemu2-arm64-compat ci-qemu2-arm64-mte ci-qemu2-riscv64 ci-snapshot-upstream-root ci-upstream-bpf-kasan-gce ci-upstream-bpf-next-kasan-gce ci-upstream-gce-arm64 ci-upstream-gce-leak ci-upstream-kasan-badwrites-root ci-upstream-kasan-gce ci-upstream-kasan-gce-386 ci-upstream-kasan-gce-root ci-upstream-kasan-gce-selinux-root ci-upstream-kasan-gce-smack-root ci-upstream-kmsan-gce-386-root ci-upstream-kmsan-gce-root ci-upstream-net-kasan-gce ci-upstream-net-this-kasan-gce ci2-upstream-fs ci2-upstream-kcsan-gce ci2-upstream-usb]
First crash: 296d, last: 8h41m
Cause bisection: introduced by (bisect log) :
commit 1d16c605cc55ef26f0c65b362665a6c99080ccbc
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Thu Nov 9 19:22:46 2023 +0000

  bcachefs: Disk space accounting rewrite

Crash: INFO: task hung in __closure_sync (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [bcachefs?] INFO: task hung in invalidate_inode_pages2_range (3) 2 (5) 2025/08/08 10:12
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in invalidate_inode_pages2_range 1 1 976d 976d 0/1 upstream: reported on 2023/01/06 10:24
upstream INFO: task hung in invalidate_inode_pages2_range (2) bcachefs 1 33 391d 422d 0/29 auto-obsoleted due to no activity on 2024/10/26 14:07
upstream INFO: task hung in invalidate_inode_pages2_range fs 1 6 2711d 2817d 0/29 auto-closed as invalid on 2019/02/22 10:34
android-49 INFO: task hung in invalidate_inode_pages2_range 1 13 2700d 2764d 0/3 auto-closed as invalid on 2019/02/22 15:29
android-44 INFO: task hung in invalidate_inode_pages2_range 1 3 2742d 2746d 0/2 auto-closed as invalid on 2019/02/22 15:29
Last patch testing requests (5)
Created Duration User Patch Repo Result
2025/08/08 09:37 8m mmpgouride@gmail.com https://github.com/alanskind/bcachefs 9191195d0412c6e190292198d4fc3d4ee996d019 error
2025/07/30 00:17 16m retest repro upstream report log
2025/07/30 00:17 19m retest repro upstream report log
2025/05/04 09:50 21m retest repro upstream report log
2025/05/04 09:50 16m retest repro upstream report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/06/04 05:14 1h57m bisect fix upstream OK (0) job log log

Sample crash report:
INFO: task syz-executor405:5830 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc2-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor405 state:D stack:16056 pid:5830  tgid:5829  ppid:5828   task_flags:0x400140 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5396 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6785
 __schedule_loop kernel/sched/core.c:6863 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6878
 io_schedule+0x81/0xe0 kernel/sched/core.c:7723
 folio_wait_bit_common+0x6b0/0xb90 mm/filemap.c:1317
 folio_lock include/linux/pagemap.h:1114 [inline]
 invalidate_inode_pages2_range+0x557/0xa80 mm/truncate.c:690
 bch2_write_invalidate_inode_pages_range+0xc5/0x110 fs/bcachefs/fs-io-pagecache.c:68
 bch2_direct_write+0x2a62/0x2ce0 fs/bcachefs/fs-io-direct.c:662
 bch2_write_iter+0x18f/0x2b90 fs/bcachefs/fs-io-buffered.c:1064
 iter_file_splice_write+0x937/0x1000 fs/splice.c:738
 do_splice_from fs/splice.c:935 [inline]
 direct_splice_actor+0x101/0x160 fs/splice.c:1158
 splice_direct_to_actor+0x5a5/0xcc0 fs/splice.c:1102
 do_splice_direct_actor fs/splice.c:1201 [inline]
 do_splice_direct+0x181/0x270 fs/splice.c:1227
 do_sendfile+0x4da/0x7e0 fs/read_write.c:1370
 __do_sys_sendfile64 fs/read_write.c:1431 [inline]
 __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1417
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4daeaa3509
RSP: 002b:00007f4daea58218 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f4daeb30608 RCX: 00007f4daeaa3509
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000005
RBP: 00007f4daeb30600 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000800000009 R11: 0000000000000246 R12: 00007f4daeafcb48
R13: 0031656c69662f2e R14: 0000200000000240 R15: 0000200000000040
 </TASK>
INFO: task syz-executor405:5842 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc2-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor405 state:D stack:24392 pid:5842  tgid:5829  ppid:5828   task_flags:0x440040 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5396 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6785
 __schedule_loop kernel/sched/core.c:6863 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6878
 __bch2_two_state_lock+0x1ea/0x370 fs/bcachefs/two_state_shared_lock.c:7
 bch2_two_state_lock fs/bcachefs/two_state_shared_lock.h:55 [inline]
 bch2_readahead+0x94f/0x1100 fs/bcachefs/fs-io-buffered.c:296
 read_pages+0x17a/0x580 mm/readahead.c:160
 page_cache_ra_order+0xa24/0xc70 mm/readahead.c:515
 filemap_get_pages+0x43c/0x1ea0 mm/filemap.c:2602
 filemap_splice_read+0x4fc/0xbc0 mm/filemap.c:2990
 do_splice_read fs/splice.c:979 [inline]
 splice_direct_to_actor+0x4a6/0xcc0 fs/splice.c:1083
 do_splice_direct_actor fs/splice.c:1201 [inline]
 do_splice_direct+0x181/0x270 fs/splice.c:1227
 do_sendfile+0x4da/0x7e0 fs/read_write.c:1370
 __do_sys_sendfile64 fs/read_write.c:1431 [inline]
 __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1417
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4daeaa3509
RSP: 002b:00007f4daea37218 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f4daeb30618 RCX: 00007f4daeaa3509
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000006
RBP: 00007f4daeb30610 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000e3aa6ea R11: 0000000000000246 R12: 00007f4daeafcb48
R13: 0031656c69662f2e R14: 0000200000000240 R15: 0000200000000040
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e13ed60 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e13ed60 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e13ed60 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6770
2 locks held by getty/5584:
 #0: ffff88814dc680a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900036bb2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
1 lock held by syz-executor405/5830:
 #0: ffff888034a78428 (sb_writers#8){.+.+}-{0:0}, at: direct_splice_actor+0x49/0x160 fs/splice.c:1157
1 lock held by syz-executor405/5842:
 #0: ffff88806c5982e8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:932 [inline]
 #0: ffff88806c5982e8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: page_cache_ra_order+0x445/0xc70 mm/readahead.c:491

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.16.0-rc2-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:307 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:470
 kthread+0x70e/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.16.0-rc2-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:pv_native_safe_halt+0x13/0x20 arch/x86/kernel/paravirt.c:82
Code: cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 0f 00 2d 23 f6 28 00 f3 0f 1e fa fb f4 <c3> cc cc cc cc cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffffff8de07d80 EFLAGS: 000002c6
RAX: 0c7705bb82258100 RBX: ffffffff81975c68 RCX: 0c7705bb82258100
RDX: 0000000000000001 RSI: ffffffff8d96e7d3 RDI: ffffffff8be1b680
RBP: ffffffff8de07ea8 R08: ffff8880b8632f5b R09: 1ffff110170c65eb
R10: dffffc0000000000 R11: ffffed10170c65ec R12: ffffffff8f9fe2f0
R13: 0000000000000000 R14: 0000000000000000 R15: 1ffffffff1bd2a50
FS:  0000000000000000(0000) GS:ffff888125c85000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ed86da7660 CR3: 000000000df38000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 arch_safe_halt arch/x86/include/asm/paravirt.h:107 [inline]
 default_idle+0x13/0x20 arch/x86/kernel/process.c:749
 default_idle_call+0x74/0xb0 kernel/sched/idle.c:117
 cpuidle_idle_call kernel/sched/idle.c:185 [inline]
 do_idle+0x1e8/0x510 kernel/sched/idle.c:325
 cpu_startup_entry+0x44/0x60 kernel/sched/idle.c:423
 rest_init+0x2de/0x300 init/main.c:745
 start_kernel+0x47d/0x500 init/main.c:1102
 x86_64_start_reservations+0x24/0x30 arch/x86/kernel/head64.c:307
 x86_64_start_kernel+0x143/0x1c0 arch/x86/kernel/head64.c:288
 common_startup_64+0x13e/0x147
 </TASK>

Crashes (53):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/16 18:54 upstream e04c78d86a96 d1716036 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/02/28 06:54 upstream 1e15510b71c9 6a8fcbc4 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/02/25 14:48 upstream d082ecbc71e9 d34966d1 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/09/08 23:31 upstream f777d1112ee5 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/22 12:45 upstream 3957a5720157 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/21 08:18 upstream 41cd3fd15263 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/20 18:03 upstream b19a97d57c15 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/19 20:27 upstream b19a97d57c15 254a27c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/19 05:02 upstream be48bcf004f9 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/17 00:09 upstream 90d970cade8e 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/16 15:15 upstream dfd4b508c8c6 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/08/16 06:46 upstream dfd4b508c8c6 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/15 23:17 upstream 155a3c003e55 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/13 01:56 upstream 3f31a806a62e 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/05 16:02 upstream a79a588fc176 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/05 13:24 upstream a79a588fc176 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/05 04:39 upstream a79a588fc176 d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/04 22:21 upstream 4c06e63b9203 d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/04 22:14 upstream 4c06e63b9203 d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/07/02 19:27 upstream b4911fb0b060 bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/28 08:12 upstream 67a993863163 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/27 00:09 upstream ee88bddf7f2f 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/26 01:40 upstream 92ca6c498a5e 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/25 14:42 upstream 7595b66ae9de 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/24 10:15 upstream 78f4e737a53e e2f27c35 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/23 09:14 upstream b67ec639010f d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/22 03:15 upstream 3f75bfff44be d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/21 14:41 upstream 11313e2f7812 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/18 06:54 upstream 4663747812d1 e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/06/16 14:46 upstream e04c78d86a96 d1716036 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/04/18 13:47 upstream fc96b232f8e7 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/04/05 22:10 upstream a8662bcd2ff1 1c65791e .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in invalidate_inode_pages2_range
2025/03/24 22:21 upstream 38fec10eb60d 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/03/22 18:04 upstream 88d324e69ea9 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/03/14 17:32 upstream 695caca9345a e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/03/12 07:46 upstream 0b46b049d6ec ee70e6db .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/03/07 18:00 upstream 00a7d39898c8 7e3bd60d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/03/03 17:37 upstream 7eb172143d55 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/02/28 03:31 upstream 1e15510b71c9 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/02/26 19:44 upstream ac9c34d1e45a d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/02/26 03:24 upstream 2a1944bff549 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/02/08 14:33 upstream 8f6629c004b1 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/01/18 20:46 upstream 595523945be0 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2024/12/28 04:32 upstream 8379578b11d5 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2024/11/16 20:30 upstream e8bdb3c8be08 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in invalidate_inode_pages2_range
2025/01/07 18:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 573067a5a685 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in invalidate_inode_pages2_range
2025/01/07 02:20 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 573067a5a685 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in invalidate_inode_pages2_range
2025/01/06 10:34 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 573067a5a685 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in invalidate_inode_pages2_range
2024/12/21 16:26 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 573067a5a685 d7f584ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in invalidate_inode_pages2_range
* Struck through repros no longer work on HEAD.