[v6.1] INFO: rcu detected stall in devlink_nl_cmd_trap_get_dumpit

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 909ba1f1b414 Linux 6.1.90
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1152b908980000
kernel config: https://syzkaller.appspot.com/x/.config?x=660c4d17e3d2ceeb
dashboard link: https://syzkaller.appspot.com/bug?extid=26e3a312aa99582005f8
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/5a4f1efb0858/disk-909ba1f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5f7faf626bf2/vmlinux-909ba1f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9d7a2826732f/Image-909ba1f1.gz.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P5803
(detected by 0, t=10502 jiffies, g=13373, q=1782 ncpus=2)
task:syz-executor.1 state:R running task stack:0 pid:5803 ppid:4676 flags:0x0000000d
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
sched_show_task+0x438/0x570 kernel/sched/core.c:8942
rcu_print_detail_task_stall_rnp kernel/rcu/tree_stall.h:261 [inline]
print_other_cpu_stall+0x1ab8/0x22e0 kernel/rcu/tree_stall.h:605
check_cpu_stall kernel/rcu/tree_stall.h:777 [inline]
rcu_pending kernel/rcu/tree.c:3890 [inline]
rcu_sched_clock_irq+0x195c/0x1c54 kernel/rcu/tree.c:2393
update_process_times+0x15c/0x1f4 kernel/time/timer.c:1869
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x340/0x4f8 kernel/time/tick-sched.c:1501
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x484/0xdc0 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x2c0/0xb64 kernel/time/hrtimer.c:1812
timer_handler drivers/clocksource/arm_arch_timer.c:655 [inline]
arch_timer_handler_virt+0x74/0x88 drivers/clocksource/arm_arch_timer.c:666
handle_percpu_devid_irq+0x174/0x354 kernel/irq/chip.c:930
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq_desc kernel/irq/irqdesc.c:651 [inline]
generic_handle_domain_irq+0x7c/0xc4 kernel/irq/irqdesc.c:707
__gic_handle_irq drivers/irqchip/irq-gic-v3.c:737 [inline]
__gic_handle_irq_from_irqson drivers/irqchip/irq-gic-v3.c:788 [inline]
gic_handle_irq+0x70/0x1e4 drivers/irqchip/irq-gic-v3.c:832
call_on_irq_stack+0x24/0x4c arch/arm64/kernel/entry.S:893
do_interrupt_handler+0xd4/0x138 arch/arm64/kernel/entry-common.c:274
__el1_irq arch/arm64/kernel/entry-common.c:471 [inline]
el1_interrupt+0x34/0x68 arch/arm64/kernel/entry-common.c:486
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:491
el1h_64_irq+0x64/0x68 arch/arm64/kernel/entry.S:581
arch_local_irq_restore+0x8/0x10 arch/arm64/include/asm/irqflags.h:122
lock_is_held include/linux/lockdep.h:283 [inline]
rcu_read_lock_held+0x34/0x50 kernel/rcu/update.c:311
xa_head include/linux/xarray.h:1182 [inline]
xas_find_marked+0x19c/0xe84 lib/xarray.c:1324
xa_find+0x238/0x3c8 lib/xarray.c:2022
devlinks_xa_find_get+0xfc/0x2dc net/devlink/leftover.c:300
devlinks_xa_find_get_first net/devlink/leftover.c:328 [inline]
devlink_nl_cmd_trap_get_dumpit+0x10c/0x504 net/devlink/leftover.c:8493
netlink_dump+0x46c/0xa78 net/netlink/af_netlink.c:2231
__netlink_dump_start+0x484/0x698 net/netlink/af_netlink.c:2335
genl_family_rcv_msg_dumpit net/netlink/genetlink.c:714 [inline]
genl_family_rcv_msg net/netlink/genetlink.c:830 [inline]
genl_rcv_msg+0x7b4/0xc2c net/netlink/genetlink.c:850
netlink_rcv_skb+0x20c/0x3b8 net/netlink/af_netlink.c:2508
genl_rcv+0x38/0x50 net/netlink/genetlink.c:861
netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline]
netlink_unicast+0x65c/0x898 net/netlink/af_netlink.c:1352
netlink_sendmsg+0x834/0xb18 net/netlink/af_netlink.c:1874
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x55c/0x848 net/socket.c:2514
___sys_sendmsg net/socket.c:2568 [inline]
__sys_sendmsg+0x26c/0x33c net/socket.c:2597
__do_sys_sendmsg net/socket.c:2606 [inline]
__se_sys_sendmsg net/socket.c:2604 [inline]
__arm64_sys_sendmsg+0x80/0x94 net/socket.c:2604
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 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