[v6.1] INFO: rcu detected stall in sendmsg (3)

Hello,

syzbot found the following issue on:

HEAD commit: c18e82d3ee44 Linux 6.1.101
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=145ee223980000
kernel config: https://syzkaller.appspot.com/x/.config?x=46d1a7a8110625db
dashboard link: https://syzkaller.appspot.com/bug?extid=c860512db72d55d7ab2b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/78271d3818f2/disk-c18e82d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8b7c8f740950/vmlinux-c18e82d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d3542200bb03/bzImage-c18e82d3.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): P5799/1:b..l
(detected by 0, t=10502 jiffies, g=28945, q=183 ncpus=2)
task:udevd state:R running task stack:25792 pid:5799 ppid:3091 flags:0x00004002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0x143f/0x4570 kernel/sched/core.c:6561
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6873
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4/0x60 kernel/kcov.c:206
Code: 00 0f 0b 0f 1f 00 53 48 89 fb e8 17 00 00 00 48 8b 3d 98 23 0f 0d 48 89 de 5b e9 07 b1 56 00 cc cc cc cc cc cc cc 48 8b 04 24 <65> 48 8b 0d a4 d3 77 7e 65 8b 15 a5 d3 77 7e f7 c2 00 01 ff 00 74
RSP: 0018:ffffc9000336f460 EFLAGS: 00000202
RAX: ffffffff8197bcd9 RBX: 0000000000000001 RCX: ffff88805d791dc0
RDX: ffff88805d791dc0 RSI: ffffffff8b5d5b40 RDI: ffffffff8b5d5b00
RBP: ffffffff8197bc92 R08: ffffffff8197bcc2 R09: fffffbfff20e7245
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88805d791dc0
R13: ffffffff817855b0 R14: 0000000000000001 R15: 00007fc879571a4b
rcu_read_lock include/linux/rcupdate.h:792 [inline]
is_bpf_text_address+0x69/0x2a0 kernel/bpf/core.c:731
kernel_text_address+0x9f/0xd0 kernel/extable.c:125
__kernel_text_address+0x9/0x40 kernel/extable.c:79
unwind_get_return_address+0x49/0x80 arch/x86/kernel/unwind_orc.c:323
arch_stack_walk+0xf3/0x140 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x65/0x70 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x52/0x3a0 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
kmem_cache_alloc_node+0x136/0x310 mm/slub.c:3443
__alloc_skb+0xde/0x670 net/core/skbuff.c:505
alloc_skb include/linux/skbuff.h:1271 [inline]
netlink_alloc_large_skb net/netlink/af_netlink.c:1198 [inline]
netlink_sendmsg+0x6f8/0xd60 net/netlink/af_netlink.c:1849
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
____sys_sendmsg+0x5a5/0x8f0 net/socket.c:2514
___sys_sendmsg net/socket.c:2568 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2597
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc879571a4b
RSP: 002b:00007fff8619dfd8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00005648a0989bd0 RCX: 00007fc879571a4b
RDX: 0000000000000000 RSI: 00007fff8619dfe8 RDI: 000000000000000c
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 000000000000010f R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000202 R14: 0000000000000000 R15: 00005648a092c910
</TASK>
rcu: rcu_preempt kthread starved for 10545 jiffies! g28945 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->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:I stack:26712 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0x143f/0x4570 kernel/sched/core.c:6561
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6873
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_reschedule_ipi+0x16/0x20 arch/x86/include/asm/idtentry.h:658
RIP: 0010:schedule_timeout+0x1b/0x300 kernel/time/timer.c:1927
Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 e4 e0 48 81 ec c0 00 00 00 49 89 ff <65> 48 8b 04 25 28 00 00 00 48 89 84 24 a0 00 00 00 49 bc 00 00 00
RSP: 0018:ffffc90000157bc0 EFLAGS: 00000286
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: ffffffff8b0c0240 RDI: 0000000000000001
RBP: ffffc90000157cb0 R08: dffffc0000000000 R09: fffffbfff1a66024
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000001
rcu_gp_fqs_loop+0x2d2/0x1150 kernel/rcu/tree.c:1706
rcu_gp_kthread+0xa3/0x3b0 kernel/rcu/tree.c:1905
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:567


---
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 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

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