From: syzbot ci <syzbot+ci25fe01996a034937@syzkaller.appspotmail.com>
To: ameryhung@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
martin.lau@linux.dev, paul.chaignon@gmail.com
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: bpf: Support non-linear skbs for BPF_PROG_TEST_RUN
Date: Sun, 14 Sep 2025 23:45:49 -0700 [thread overview]
Message-ID: <68c7b61d.050a0220.3c6139.08de.GAE@google.com> (raw)
In-Reply-To: <cover.1757862238.git.paul.chaignon@gmail.com>
syzbot ci has tested the following series
[v2] bpf: Support non-linear skbs for BPF_PROG_TEST_RUN
https://lore.kernel.org/all/cover.1757862238.git.paul.chaignon@gmail.com
* [PATCH bpf-next v2 1/4] bpf: Refactor cleanup of bpf_prog_test_run_skb
* [PATCH bpf-next v2 2/4] bpf: Craft non-linear skbs in BPF_PROG_TEST_RUN
* [PATCH bpf-next v2 3/4] selftests/bpf: Support non-linear flag in test loader
* [PATCH bpf-next v2 4/4] selftests/bpf: Test direct packet access on non-linear skbs
and found the following issue:
kernel BUG in bpf_test_init
Full report is available here:
https://ci.syzbot.org/series/23791187-8fc0-4c8a-bebc-3909e311c11e
***
kernel BUG in bpf_test_init
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: a578b54a8ad282dd739e4d1f4e8352fc8ac1c4a0
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/037e1e74-be70-4216-ad05-430c2deea0bb/config
C repro: https://ci.syzbot.org/findings/adf84c1c-28ba-48f5-9638-8339635cebe5/c_repro
syz repro: https://ci.syzbot.org/findings/adf84c1c-28ba-48f5-9638-8339635cebe5/syz_repro
------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:28!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 6014 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:__phys_addr+0x173/0x180 arch/x86/mm/physaddr.c:28
Code: e8 02 2a 4b 00 48 c7 c7 50 d1 fa 8d 48 89 de 4c 89 f2 e8 e0 2f 8b 03 e9 4d ff ff ff e8 e6 29 4b 00 90 0f 0b e8 de 29 4b 00 90 <0f> 0b e8 d6 29 4b 00 90 0f 0b 0f 1f 00 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900032d7b68 EFLAGS: 00010293
RAX: ffffffff81749722 RBX: 00006180047f3080 RCX: ffff8881079b9cc0
RDX: 0000000000000000 RSI: 0000000000000061 RDI: 0000000000000000
RBP: 00000000000000db R08: ffff88811fcc20da R09: 0000000000000000
R10: ffff88811fcc2000 R11: ffffed1023f9841c R12: 00000000000000db
R13: 00000000000000db R14: 0000000000000028 R15: 0000000000000061
FS: 000055557464c500(0000) GS:ffff8881a3c13000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000001f984000 CR4: 00000000000006f0
Call Trace:
<TASK>
virt_to_folio include/linux/mm.h:1180 [inline]
kfree+0x77/0x440 mm/slub.c:4886
bpf_test_init+0x1ba/0x220 net/bpf/test_run.c:686
bpf_prog_test_run_skb+0x2c8/0x1700 net/bpf/test_run.c:1039
bpf_prog_test_run+0x2c7/0x340 kernel/bpf/syscall.c:4590
__sys_bpf+0x581/0x870 kernel/bpf/syscall.c:6047
__do_sys_bpf kernel/bpf/syscall.c:6139 [inline]
__se_sys_bpf kernel/bpf/syscall.c:6137 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:6137
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f502198eba9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd90d34788 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f5021bd5fa0 RCX: 00007f502198eba9
RDX: 0000000000000050 RSI: 0000200000000240 RDI: 000000000000000a
RBP: 00007f5021a11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5021bd5fa0 R14: 00007f5021bd5fa0 R15: 0000000000000003
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__phys_addr+0x173/0x180 arch/x86/mm/physaddr.c:28
Code: e8 02 2a 4b 00 48 c7 c7 50 d1 fa 8d 48 89 de 4c 89 f2 e8 e0 2f 8b 03 e9 4d ff ff ff e8 e6 29 4b 00 90 0f 0b e8 de 29 4b 00 90 <0f> 0b e8 d6 29 4b 00 90 0f 0b 0f 1f 00 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900032d7b68 EFLAGS: 00010293
RAX: ffffffff81749722 RBX: 00006180047f3080 RCX: ffff8881079b9cc0
RDX: 0000000000000000 RSI: 0000000000000061 RDI: 0000000000000000
RBP: 00000000000000db R08: ffff88811fcc20da R09: 0000000000000000
R10: ffff88811fcc2000 R11: ffffed1023f9841c R12: 00000000000000db
R13: 00000000000000db R14: 0000000000000028 R15: 0000000000000061
FS: 000055557464c500(0000) GS:ffff8881a3c13000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000001f984000 CR4: 00000000000006f0
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
next prev parent reply other threads:[~2025-09-15 6:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 15:08 [PATCH bpf-next v2 0/4] bpf: Support non-linear skbs for BPF_PROG_TEST_RUN Paul Chaignon
2025-09-14 15:09 ` [PATCH bpf-next v2 1/4] bpf: Refactor cleanup of bpf_prog_test_run_skb Paul Chaignon
2025-09-14 15:10 ` [PATCH bpf-next v2 2/4] bpf: Craft non-linear skbs in BPF_PROG_TEST_RUN Paul Chaignon
2025-09-16 0:27 ` Amery Hung
2025-09-17 22:06 ` Paul Chaignon
2025-09-18 17:10 ` Amery Hung
2025-09-14 15:11 ` [PATCH bpf-next v2 3/4] selftests/bpf: Support non-linear flag in test loader Paul Chaignon
2025-09-14 15:13 ` [PATCH bpf-next v2 4/4] selftests/bpf: Test direct packet access on non-linear skbs Paul Chaignon
2025-09-15 6:45 ` syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-04 12:07 [PATCH bpf-next 0/4] bpf: Support non-linear skbs for BPF_PROG_TEST_RUN Paul Chaignon
2025-09-04 18:08 ` [syzbot ci] " syzbot ci
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68c7b61d.050a0220.3c6139.08de.GAE@google.com \
--to=syzbot+ci25fe01996a034937@syzkaller.appspotmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@linux.dev \
--cc=paul.chaignon@gmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox