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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dcbcab9d7079 Linux 6.1.174
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=141f81a6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=24f81a96894a6c85df30
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/875b85cc4d29/disk-dcbcab9d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1d8bb5e74691/vmlinux-dcbcab9d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7d919271a601/bzImage-dcbcab9d.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 2662 jiffies s: 200621 root: 0x1/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 6422 Comm: syz.4.9012 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:perf_trace_run_bpf_submit+0x3/0x1c0 kernel/events/core.c:10024
Code: e8 62 76 93 02 e9 15 ff ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 42 ff ff ff 48 89 df e8 45 e0 2d 00 e9 35 ff ff ff 55 41 57 <41> 56 41 55 41 54 53 48 83 ec 10 4d 89 ce 4c 89 44 24 08 49 89 cd
RSP: 0018:ffffc90000007a38 EFLAGS: 00000046
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: ffffffff8cb80420
RDX: 0000000000000001 RSI: 0000000000000014 RDI: ffffe8ffffa1b000
RBP: ffffc90000007b28 R08: 0000000000000001 R09: ffff8880b8e35558
R10: dffffc0000000000 R11: ffffed10171c6b02 R12: 0000000009400e86
R13: ffffe8ffffa1b00c R14: ffffe8ffffa1b000 R15: 1ffff92000000f50
FS: 00007f200a7136c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffcccdbfe70 CR3: 0000000066b8d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000008d24 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<IRQ>
perf_trace_preemptirq_template+0x268/0x320 include/trace/events/preemptirq.h:14
trace_irq_enable_rcuidle+0xd3/0x140 include/trace/events/preemptirq.h:40
trace_hardirqs_on+0x24/0x40 kernel/trace/trace_preemptirq.c:44
asm_sysvec_irq_work+0x16/0x20 arch/x86/include/asm/idtentry.h:728
RIP: 0010:rcu_read_unlock_special+0x7f/0x510 kernel/rcu/tree_plugin.h:685
Code: eb 03 48 b8 f1 f1 f1 f1 f8 f2 f2 f2 4a 89 04 2b 42 c7 44 2b 08 f8 f3 f3 f3 65 44 8b 35 82 22 95 7e 41 f7 c6 00 00 f0 00 74 40 <48> c7 44 24 40 0e 36 e0 45 4a c7 04 2b 00 00 00 00 42 c7 44 2b 08
RSP: 0018:ffffc90000007c20 EFLAGS: 00000206
RAX: 8bd4992ef809fe00 RBX: 1ffff92000000f8c RCX: 8bd4992ef809fe00
RDX: dffffc0000000000 RSI: ffffffff8a8c19a0 RDI: ffffffff8adf1ba0
RBP: ffffc90000007d08 R08: ffffffff90afa24f R09: 1ffffffff215f449
R10: dffffc0000000000 R11: fffffbfff215f44a R12: 0000000000000246
R13: dffffc0000000000 R14: ffff8880b8e3b900 R15: 0000000000000001
__rcu_read_unlock+0x78/0xd0 kernel/rcu/tree_plugin.h:426
rcu_read_unlock include/linux/rcupdate.h:823 [inline]
rebalance_domains+0x8da/0xa10 kernel/sched/fair.c:11051
handle_softirqs+0x2a1/0x930 kernel/softirq.c:596
__do_softirq kernel/softirq.c:630 [inline]
invoke_softirq kernel/softirq.c:470 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679
irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:siw_netdev_event+0x94/0x4e0 drivers/infiniband/sw/siw/siw_main.c:434
Code: 72 a3 e4 f9 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 9c af 35 fa 48 8b 1b 0f 1f 44 00 00 e8 4f a3 e4 f9 48 89 df <be> 12 00 00 00 e8 02 a7 d9 ff 48 85 c0 74 66 49 89 c6 48 89 c3 4c
RSP: 0018:ffffc90004b0f820 EFLAGS: 00000283
RAX: ffffffff879de361 RBX: ffff888083c92000 RCX: 0000000000080000
RDX: ffffc900143ce000 RSI: 000000000000eae9 RDI: ffff888083c92000
RBP: ffffc90004b0f8e0 R08: ffff888088763b80 R09: 0000000000000004
R10: 000000000000000a R11: 0000000000000002 R12: dffffc0000000000
R13: 1ffff92000961f08 R14: dffffc0000000000 R15: 0000000000000004
notifier_call_chain kernel/notifier.c:87 [inline]
raw_notifier_call_chain+0xcb/0x160 kernel/notifier.c:455
__dev_notify_flags+0x245/0x310 net/core/dev.c:8729
dev_change_flags+0xe4/0x1a0 net/core/dev.c:8753
devinet_ioctl+0x911/0x1af0 net/ipv4/devinet.c:1156
inet_ioctl+0x2fa/0x460 net/ipv4/af_inet.c:1008
sock_do_ioctl+0xfb/0x320 net/socket.c:1201
sock_ioctl+0x4d2/0x710 net/socket.c:1320
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f200979ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f200a713028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2009a15fa0 RCX: 00007f200979ce59
RDX: 0000200000000180 RSI: 0000000000008914 RDI: 0000000000000008
RBP: 00007f2009832d6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2009a16038 R14: 00007f2009a15fa0 R15: 00007fff61c0e038
</TASK>


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