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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 80efc6265290 Linux 5.15.150
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111633ca180000
kernel config: https://syzkaller.appspot.com/x/.config?x=928a06454760df60
dashboard link: https://syzkaller.appspot.com/bug?extid=7fbca9615641a39d3919
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=122b89a2180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d1e874180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4d9deaf11f6d/disk-80efc626.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a663ca82b421/vmlinux-80efc626.xz
kernel image: https://storage.googleapis.com/syzbot-assets/83c042113dee/bzImage-80efc626.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...0: (1 ticks this GP) idle=9a5/1/0x4000000000000000 softirq=4277/4277 fqs=5250
(detected by 1, t=10502 jiffies, g=3565, q=270)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3528 Comm: syz-executor291 Not tainted 5.15.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:preempt_count arch/x86/include/asm/preempt.h:27 [inline]
RIP: 0010:check_kcov_mode kernel/kcov.c:163 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0xc/0x60 kernel/kcov.c:197
Code: 89 fb e8 17 00 00 00 48 8b 3d d8 58 63 0c 48 89 de 5b e9 57 e5 48 00 cc cc cc cc cc cc cc 48 8b 04 24 65 48 8b 0d 24 3a 82 7e <65> 8b 15 25 3a 82 7e f7 c2 00 01 ff 00 74 11 f7 c2 00 01 00 00 74
RSP: 0018:ffffc90000007d38 EFLAGS: 00000046
RAX: ffffffff816f6ccc RBX: ffff888078ef9b40 RCX: ffff888018babb80
RDX: 0000000080010001 RSI: 0000000000000001 RDI: ffff888078ef9b40
RBP: ffffc90000007eb0 R08: ffffffff816f3c5c R09: ffff888078ef9b48
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880b9a2a200
R13: ffff8880b9a2a300 R14: ffff888078ef9b40 R15: dffffc0000000000
FS: 0000555555dc2380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000600 CR3: 0000000070d7f000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
debug_deactivate+0xc/0x1e0 kernel/time/hrtimer.c:480
__run_hrtimer kernel/time/hrtimer.c:1654 [inline]
__hrtimer_run_queues+0x31d/0xcf0 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1085 [inline]
__sysvec_apic_timer_interrupt+0x139/0x470 arch/x86/kernel/apic/apic.c:1102
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:native_irq_disable arch/x86/include/asm/irqflags.h:40 [inline]
RIP: 0010:arch_local_irq_disable arch/x86/include/asm/irqflags.h:75 [inline]
RIP: 0010:arch_local_irq_save arch/x86/include/asm/irqflags.h:107 [inline]
RIP: 0010:lock_is_held_type+0x69/0x180 kernel/locking/lockdep.c:5662
Code: 8b 2d 2b d4 e6 75 41 83 bd ec 0a 00 00 00 0f 85 db 00 00 00 41 89 f6 49 89 ff 48 c7 04 24 00 00 00 00 9c 8f 04 24 4c 8b 24 24 <fa> 48 c7 c7 00 23 8b 8a e8 1a 12 00 00 65 ff 05 33 dd e6 75 41 83
RSP: 0018:ffffc900021e7c48 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffffffff8c947bc0 RCX: 0000000080000000
RDX: ffff888018babb80 RSI: 00000000ffffffff RDI: ffffffff8c91f720
RBP: 00000000ffffffff R08: ffffffff8178bafb R09: fffffbfff1f79e19
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000246
R13: ffff888018babb80 R14: 00000000ffffffff R15: ffffffff8c91f720
task_css_set include/linux/cgroup.h:483 [inline]
cgroup_sk_alloc+0x1e5/0x3c0 kernel/cgroup/cgroup.c:6734
sk_alloc+0x204/0x310 net/core/sock.c:1925
__netlink_create+0x6b/0x2c0 net/netlink/af_netlink.c:647
netlink_create+0x3a9/0x500 net/netlink/af_netlink.c:710
__sock_create+0x460/0x8d0 net/socket.c:1486
sock_create net/socket.c:1537 [inline]
__sys_socket+0x132/0x370 net/socket.c:1579
__do_sys_socket net/socket.c:1588 [inline]
__se_sys_socket net/socket.c:1586 [inline]
__x64_sys_socket+0x76/0x80 net/socket.c:1586
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fcb92be1ee9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 d1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff75d2b908 EFLAGS: 00000246 ORIG_RAX: 0000000000000029
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcb92be1ee9
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000010
RBP: 00000000000f4240 R08: 0000000100000000 R09: 0000000100000000
R10: 0000000100000000 R11: 0000000000000246 R12: 00007fff75d2b960
R13: 000000000002f98a R14: 00007fff75d2b92c R15: 0000000000000003
</TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.417 msecs


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