[v5.15] INFO: rcu detected stall in handle_mm_fault (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ddcaf4999061 Linux 5.15.147
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11812c6fe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab92786ed9f7c373
dashboard link: https://syzkaller.appspot.com/bug?extid=0635fee446a22fbe82ad
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=177e55c7e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15169c6fe80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f538e3b5b6b/disk-ddcaf499.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/aff958e6c838/vmlinux-ddcaf499.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b812c40b66fa/Image-ddcaf499.gz.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P4002/1:b..l
(detected by 0, t=10502 jiffies, g=2925, q=62)
task:syz-executor620 state:R running task stack: 0 pid: 4002 ppid: 3976 flags:0x00000004
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
preempt_schedule_irq+0x90/0x274 kernel/sched/core.c:6780
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:580
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
count_memcg_events include/linux/memcontrol.h:1058 [inline]
count_memcg_event_mm+0x1d0/0x308 include/linux/memcontrol.h:1081
handle_mm_fault+0x1c4/0x3424 mm/memory.c:4834
__do_page_fault arch/arm64/mm/fault.c:505 [inline]
do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605
do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819
el0_da+0x94/0x20c arch/arm64/kernel/entry-common.c:494
el0t_64_sync_handler+0xc0/0xe4 arch/arm64/kernel/entry-common.c:629
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
rcu: rcu_preempt kthread timer wakeup didn't happen for 10503 jiffies! g2925 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=0 timer-softirq=752
rcu: rcu_preempt kthread starved for 10504 jiffies! g2925 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
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:I 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:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
schedule_timeout+0x1d8/0x344 kernel/time/timer.c:1884
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:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
rcu: Stack dump where RCU GP kthread last ran:
Task dump for CPU 0:
task:syz-executor620 state:R running task stack: 0 pid: 4000 ppid: 3980 flags:0x00000001
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:8640
dump_cpu_task+0x84/0xa8 kernel/sched/core.c:10914
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:1788
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:1685 [inline]
__hrtimer_run_queues+0x458/0xca4 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x2c0/0xb64 kernel/time/hrtimer.c:1811
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:933
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq_desc kernel/irq/irqdesc.c:651 [inline]
handle_domain_irq+0xec/0x178 kernel/irq/irqdesc.c:706
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
el1_interrupt+0x30/0x58 arch/arm64/kernel/entry-common.c:454
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:470
el1h_64_irq+0x78/0x7c arch/arm64/kernel/entry.S:580
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
lock_acquire+0x280/0x77c kernel/locking/lockdep.c:5626
__might_fault+0xc8/0x128 mm/memory.c:5324
setup_sigframe arch/arm64/kernel/signal.c:627 [inline]
setup_rt_frame arch/arm64/kernel/signal.c:789 [inline]
handle_signal arch/arm64/kernel/signal.c:830 [inline]
do_signal arch/arm64/kernel/signal.c:905 [inline]
do_notify_resume+0xf18/0x32b8 arch/arm64/kernel/signal.c:943
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xfc/0x1f0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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