[v5.15] INFO: rcu detected stall in vfs_fallocate

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12892580580000
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=cbdd45ed90bf43f2dd34
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+cbdd45...@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P4149/1:b..l
(detected by 1, t=10502 jiffies, g=10293, q=145)
task:syz.1.6 state:R running task stack: 0 pid: 4149 ppid: 4021 flags:0x00000009
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5027 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6373
preempt_schedule_irq+0x90/0x274 kernel/sched/core.c:6777
arm64_preempt_schedule_irq+0x174/0x2c4 arch/arm64/kernel/entry-common.c:260
el1_interrupt+0x40/0x58 arch/arm64/kernel/entry-common.c:463
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:470
el1h_64_irq+0x78/0x7c arch/arm64/kernel/entry.S:522
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
lock_acquire+0x280/0x77c kernel/locking/lockdep.c:5626
rcu_lock_acquire+0x40/0x4c include/linux/rcupdate.h:312
rcu_read_lock include/linux/rcupdate.h:739 [inline]
mapping_get_entry mm/filemap.c:1823 [inline]
pagecache_get_page+0x164/0xd94 mm/filemap.c:1894
f2fs_grab_cache_page+0x54/0x498
f2fs_get_read_data_page+0xf8/0x860 fs/f2fs/data.c:1172
gc_data_segment fs/f2fs/gc.c:1504 [inline]
do_garbage_collect+0x43ac/0x6ddc fs/f2fs/gc.c:1671
f2fs_gc+0x7f0/0x188c fs/f2fs/gc.c:1765
f2fs_balance_fs+0x400/0x6a0 fs/f2fs/segment.c:529
f2fs_map_blocks+0x20d8/0x31f0 fs/f2fs/data.c:1700
expand_inode_data+0x474/0x858 fs/f2fs/file.c:1706
f2fs_fallocate+0x350/0x898 fs/f2fs/file.c:1802
vfs_fallocate+0x478/0x5b4 fs/open.c:308
ioctl_preallocate+0x2a0/0x34c fs/ioctl.c:294
do_vfs_ioctl+0x1d00/0x2a38 fs/ioctl.c:853
__do_sys_ioctl fs/ioctl.c:872 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0xe4/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
rcu: rcu_preempt kthread starved for 10490 jiffies! g10293 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack: 0 pid: 15 ppid: 2 flags:0x00000008
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5027 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6373
schedule+0x11c/0x1c8 kernel/sched/core.c:6456
schedule_timeout+0x1d8/0x344 kernel/time/timer.c:1914
rcu_gp_fqs_loop+0x26c/0x13d4 kernel/rcu/tree.c:1972
rcu_gp_kthread+0xc4/0x2c4 kernel/rcu/tree.c:2145
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
rcu: Stack dump where RCU GP kthread last ran:
Task dump for CPU 1:
task:syz.1.329 state:R running task stack: 0 pid: 5207 ppid: 4286 flags:0x00000000
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
sched_show_task+0x43c/0x574 kernel/sched/core.c:8637
dump_cpu_task+0x84/0xa8 kernel/sched/core.c:10924
rcu_check_gp_kthread_starvation+0x1f0/0x254 kernel/rcu/tree_stall.h:488
print_other_cpu_stall+0x202c/0x2290 kernel/rcu/tree_stall.h:592
check_cpu_stall kernel/rcu/tree_stall.h:745 [inline]
rcu_pending kernel/rcu/tree.c:3932 [inline]
rcu_sched_clock_irq+0x1894/0x1b8c kernel/rcu/tree.c:2619
update_process_times+0x1d4/0x270 kernel/time/timer.c:1818
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x340/0x4f8 kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1688 [inline]
__hrtimer_run_queues+0x458/0xca4 kernel/time/hrtimer.c:1752
hrtimer_interrupt+0x2c0/0xb64 kernel/time/hrtimer.c:1814
timer_handler drivers/clocksource/arm_arch_timer.c:659 [inline]
arch_timer_handler_virt+0x74/0x88 drivers/clocksource/arm_arch_timer.c:670
handle_percpu_devid_irq+0x29c/0x7fc kernel/irq/chip.c:930
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq_desc kernel/irq/irqdesc.c:652 [inline]
handle_domain_irq+0xec/0x178 kernel/irq/irqdesc.c:707
gic_handle_irq+0x78/0x1c8 drivers/irqchip/irq-gic-v3.c:758
call_on_irq_stack+0x24/0x4c arch/arm64/kernel/entry.S:899
do_interrupt_handler+0x74/0x94 arch/arm64/kernel/entry-common.c:267
el0_interrupt+0x98/0x2d4 arch/arm64/kernel/entry-common.c:683
__el0_irq_handler_common+0x18/0x24 arch/arm64/kernel/entry-common.c:690
el0t_64_irq_handler+0x10/0x1c arch/arm64/kernel/entry-common.c:695
el0t_64_irq+0x1a0/0x1a4 arch/arm64/kernel/entry.S:585


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.