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

1 view
Skip to first unread message

syzbot

unread,
Mar 25, 2024, 11:49:28 PMMar 25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d7543167affd Linux 6.1.82
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11963185180000
kernel config: https://syzkaller.appspot.com/x/.config?x=59059e181681c079
dashboard link: https://syzkaller.appspot.com/bug?extid=c3d3a860764c69285db0
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/88220954516a/disk-d7543167.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9062e074717/vmlinux-d7543167.xz
kernel image: https://storage.googleapis.com/syzbot-assets/70391b45a752/bzImage-d7543167.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P5290
(detected by 0, t=10502 jiffies, g=166137, q=2752 ncpus=2)
task:syz-executor.3 state:R running task stack:25280 pid:5290 ppid:2174 flags:0x00004006
Call Trace:
<IRQ>
sched_show_task+0x4d5/0x670 kernel/sched/core.c:8942
rcu_print_detail_task_stall_rnp kernel/rcu/tree_stall.h:261 [inline]
print_other_cpu_stall+0x1299/0x1640 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+0xad8/0x11f0 kernel/rcu/tree.c:2393
update_process_times+0x147/0x1b0 kernel/time/timer.c:1839
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x386/0x550 kernel/time/tick-sched.c:1501
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x5a7/0xe50 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:lock_is_held_type+0x137/0x180
Code: 75 40 48 c7 04 24 00 00 00 00 9c 8f 04 24 f7 04 24 00 02 00 00 75 46 41 f7 c4 00 02 00 00 74 01 fb 65 48 8b 04 25 28 00 00 00 <48> 3b 44 24 08 75 3c 89 e8 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f
RSP: 0018:ffffc900048a71e0 EFLAGS: 00000206
RAX: fc0df67723ebde00 RBX: 0000000000000003 RCX: ffff888025c43b80
RDX: ffff888025c43b80 RSI: ffffffff8aebffc0 RDI: ffffffff8b3d2b40
RBP: 0000000000000000 R08: ffffffff8a86306f R09: fffffbfff2092c45
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000246
R13: ffff888025c43b80 R14: 00000000ffffffff R15: ffffffff8e3d1c38
lock_is_held include/linux/lockdep.h:283 [inline]
xa_entry include/linux/xarray.h:1198 [inline]
xas_find_marked+0x364/0x10e0 lib/xarray.c:1349
xa_find+0x251/0x420 lib/xarray.c:2022
devlinks_xa_find_get+0xf2/0x2d0 net/devlink/leftover.c:300
devlinks_xa_find_get_first net/devlink/leftover.c:328 [inline]
devlink_get_from_attrs+0x101/0x320 net/devlink/leftover.c:364
devlink_nl_pre_doit+0x69/0xa50 net/devlink/leftover.c:780
genl_family_rcv_msg_doit net/netlink/genetlink.c:751 [inline]
genl_family_rcv_msg net/netlink/genetlink.c:833 [inline]
genl_rcv_msg+0xbc1/0xf70 net/netlink/genetlink.c:850
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2508
genl_rcv+0x24/0x40 net/netlink/genetlink.c:861
netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline]
netlink_unicast+0x7d8/0x970 net/netlink/af_netlink.c:1352
netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1874
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+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f201ce7dda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f201db720c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f201cfabf80 RCX: 00007f201ce7dda9
RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003
RBP: 00007f201ceca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f201cfabf80 R15: 00007ffc32377028
</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
Reply all
Reply to author
Forward
0 new messages