From: syzbot ci <syzbot+ci45b4400a7c00010b@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: xdp: RX checksum metadata hint and checksum assertion over redirect
Date: Tue, 30 Jun 2026 20:08:49 -0700 [thread overview]
Message-ID: <6a4484c1.6124255a.dd83.000b.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] xdp: RX checksum metadata hint and checksum assertion over redirect
https://lore.kernel.org/all/20260630191510.81402-1-deliran@verdict.gg
* [RFC PATCH bpf-next v1 1/7] xdp: let XDP programs assert the RX checksum over redirect
* [RFC PATCH bpf-next v1 2/7] selftests/bpf: add test for bpf_xdp_assert_rx_csum over cpumap
* [RFC PATCH bpf-next v1 3/7] xdp: add bpf_xdp_metadata_rx_csum() RX metadata kfunc
* [RFC PATCH bpf-next v1 4/7] net/mlx5e: support the rx_csum XDP metadata hint
* [RFC PATCH bpf-next v1 5/7] ice: support the rx_csum XDP metadata hint
* [RFC PATCH bpf-next v1 6/7] veth: support the rx_csum XDP metadata hint
* [RFC PATCH bpf-next v1 7/7] selftests/bpf: cover bpf_xdp_metadata_rx_csum in xdp_metadata
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/934c1801-592e-4efe-b829-7fb2af36a272
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: f456c1922c49e6be5ce407ddb74a6e61af5b65cf
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/ff08f58d-c28a-4b82-b8e6-4fda286f0e7d/config
drivers/net/ethernet/intel/ice/ice_txrx_lib.c:618:37: error: member reference base type 'const void' is not a structure or union
***
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.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[andrii@kernel.org ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net deliran@verdict.gg hawk@kernel.org john.fastabend@gmail.com kuba@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-07-01 3:08 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=6a4484c1.6124255a.dd83.000b.GAE@google.com \
--to=syzbot+ci45b4400a7c00010b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.