Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci9e3e9a66b6774b57@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Add the the capability to load HW RX checsum in eBPF programs
Date: Thu, 25 Sep 2025 03:36:58 -0700	[thread overview]
Message-ID: <68d51b4a.050a0220.25d7ab.0009.GAE@google.com> (raw)

syzbot ci has tested the following series

[v2] Add the the capability to load HW RX checsum in eBPF programs
https://lore.kernel.org/all/20250925-bpf-xdp-meta-rxcksum-v2-0-6b3fe987ce91@kernel.org
* [PATCH RFC bpf-next v2 1/5] netlink: specs: Add XDP RX checksum capability to XDP metadata specs
* [PATCH RFC bpf-next v2 2/5] net: veth: Add xmo_rx_checksum callback to veth driver
* [PATCH RFC bpf-next v2 3/5] net: ice: Add xmo_rx_checksum callback
* [PATCH RFC bpf-next v2 4/5] selftests/bpf: Add selftest support for bpf_xdp_metadata_rx_checksum
* [PATCH RFC bpf-next v2 5/5] selftests/bpf: Add bpf_xdp_metadata_rx_checksum support to xdp_hw_metadat prog

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/78ddd54f-1223-4988-a9c0-567175908ef4

***

kernel build error

tree:      bpf-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base:      d4680a11e14c7baf683cb8453d91d71d2e0b9d3e
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/ee405b1d-3849-4def-bcc7-e6b23da5f79b/config

net/core/netdev-genl.c:50:1: error: use of undeclared identifier 'NETDEV_XDP_RX_METADATA_CHECKSUM'; did you mean 'NETDEV_XDP_RX_METADATA_HASH'?

***

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:
[aleksander.lobakin@intel.com andrew@lunn.ch andrii@kernel.org anthony.l.nguyen@intel.com ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net davem@davemloft.net donald.hunter@gmail.com eddyz87@gmail.com edumazet@google.com haoluo@google.com hawk@kernel.org horms@kernel.org intel-wired-lan@lists.osuosl.org john.fastabend@gmail.com jolsa@kernel.org kpsingh@kernel.org kuba@kernel.org linux-kselftest@vger.kernel.org lorenzo@kernel.org maciej.fijalkowski@intel.com martin.lau@linux.dev netdev@vger.kernel.org pabeni@redhat.com przemyslaw.kitszel@intel.com sdf@fomichev.me shuah@kernel.org song@kernel.org yonghong.song@linux.dev]

If the report looks fine to you, reply with:
#syz upstream


             reply	other threads:[~2025-09-25 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 10:36 syzbot ci [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-20 12:54 [moderation/CI] Re: Add the the capability to load HW RX checsum in eBPF programs 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=68d51b4a.050a0220.25d7ab.0009.GAE@google.com \
    --to=syzbot+ci9e3e9a66b6774b57@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