From: syzbot ci <syzbot+cif11bedf737b79b05@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: bpf: cpumap: add missing XDP_ABORTED handling in xdp prog runner
Date: Tue, 17 Feb 2026 21:21:27 -0800 [thread overview]
Message-ID: <69954c57.a70a0220.2c38d7.0115.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] bpf: cpumap: add missing XDP_ABORTED handling in xdp prog runner
https://lore.kernel.org/all/20260218041745.36791-1-anandkrshawheritage@gmail.com
* [PATCH v2] bpf: cpumap: add missing XDP_ABORTED handling in xdp prog runner
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/007d5149-2d7a-49f1-8701-7130cda73b77
***
kernel build error
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 4c51f90d45dca71e7974ed5a7c40b9c04a6c6762
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/18e86f1d-f044-49fe-9b02-b0032587da93/config
kernel/bpf/devmap.c:349:27: error: no member named 'queue_index' in 'struct xdp_frame'
***
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.
The email will later be sent to:
[anandkrshawheritage@gmail.com andrii@kernel.org ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net davem@davemloft.net hawk@kernel.org john.fastabend@gmail.com kuba@kernel.org linux-kernel@vger.kernel.org martin.lau@linux.dev netdev@vger.kernel.org sdf@fomichev.me]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-02-18 5:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69954c57.a70a0220.2c38d7.0115.GAE@google.com \
--to=syzbot+cif11bedf737b79b05@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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