[v5.15] INFO: task hung in bpf_xdp_link_attach

0 views
Skip to first unread message

syzbot

unread,
Jun 18, 2024, 9:39:19 PM (2 days ago) Jun 18
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4878aadf2d15 Linux 5.15.161
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15017012980000
kernel config: https://syzkaller.appspot.com/x/.config?x=875d98826c53bf16
dashboard link: https://syzkaller.appspot.com/bug?extid=614348d3e19a1e0e0129
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/f227a150ea92/disk-4878aadf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6cfc50bf8b4e/vmlinux-4878aadf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23f7adc3c761/bzImage-4878aadf.xz

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

INFO: task syz-executor.1:5773 blocked for more than 143 seconds.
Not tainted 5.15.161-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:25848 pid: 5773 ppid: 3534 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
bpf_xdp_link_attach+0xdb/0x440 net/core/dev.c:9723
link_create+0x49d/0x640 kernel/bpf/syscall.c:4322
__sys_bpf+0x598/0x670 kernel/bpf/syscall.c:4721
__do_sys_bpf kernel/bpf/syscall.c:4755 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4753 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4753
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fbbb691bf29
RSP: 002b:00007fbbb54950c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fbbb6a52f80 RCX: 00007fbbb691bf29
RDX: 0000000000000040 RSI: 0000000020000100 RDI: 000000000000001c
RBP: 00007fbbb698b074 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fbbb6a52f80 R15: 00007ffd7069e398


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