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

Hello,

syzbot found the following issue on:

HEAD commit: fa93fa65db6e Linux 5.15.165
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1576e339980000
kernel config: https://syzkaller.appspot.com/x/.config?x=943cc31effce7816
dashboard link: https://syzkaller.appspot.com/bug?extid=e5beaea4288bdc45b1fe
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=13b6cab7980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9c2ccb656fbe/disk-fa93fa65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/385d10a22918/vmlinux-fa93fa65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dbf03e13a732/Image-fa93fa65.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P7/1:b..l
(detected by 0, t=10502 jiffies, g=6005, q=123)
task:kworker/0:0 state:R running task stack: 0 pid: 7 ppid: 2 flags:0x00000008
Workqueue: events nsim_fib_event_work
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
rht_key_hashfn include/linux/rhashtable.h:159 [inline]
__rhashtable_lookup include/linux/rhashtable.h:596 [inline]
rhashtable_lookup include/linux/rhashtable.h:638 [inline]
rhashtable_lookup_fast+0x244/0x814 include/linux/rhashtable.h:664
nsim_fib_rt_lookup drivers/net/netdevsim/fib.c:269 [inline]
nsim_fib6_rt_lookup drivers/net/netdevsim/fib.c:592 [inline]
nsim_fib6_rt_insert drivers/net/netdevsim/fib.c:755 [inline]
nsim_fib6_event drivers/net/netdevsim/fib.c:854 [inline]
nsim_fib_event drivers/net/netdevsim/fib.c:887 [inline]
nsim_fib_event_work+0x1f68/0x33c4 drivers/net/netdevsim/fib.c:1481
process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
process_scheduled_works kernel/workqueue.c:2373 [inline]
worker_thread+0xb88/0x1034 kernel/workqueue.c:2459
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
rcu: rcu_preempt kthread starved for 10500 jiffies! g6005 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.16 state:R running task stack: 0 pid: 4260 ppid: 4114 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
0xffff0000cccd8a30


---
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 [email protected].

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