From: syzbot ci <syzbot+ci454bc7cba78429ac@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: virtio_net: Add ethtool flow rules support
Date: Mon, 13 Oct 2025 10:54:52 -0700 [thread overview]
Message-ID: <68ed3cec.050a0220.91a22.01e9.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] virtio_net: Add ethtool flow rules support
https://lore.kernel.org/all/20251013152742.619423-1-danielj@nvidia.com
* [PATCH net-next v4 01/12] virtio_pci: Remove supported_cap size build assert
* [PATCH net-next v4 02/12] virtio: Add config_op for admin commands
* [PATCH net-next v4 03/12] virtio: Expose generic device capability operations
* [PATCH net-next v4 04/12] virtio: Expose object create and destroy API
* [PATCH net-next v4 05/12] virtio_net: Query and set flow filter caps
* [PATCH net-next v4 06/12] virtio_net: Create a FF group for ethtool steering
* [PATCH net-next v4 07/12] virtio_net: Implement layer 2 ethtool flow rules
* [PATCH net-next v4 08/12] virtio_net: Use existing classifier if possible
* [PATCH net-next v4 09/12] virtio_net: Implement IPv4 ethtool flow rules
* [PATCH net-next v4 10/12] virtio_net: Add support for IPv6 ethtool steering
* [PATCH net-next v4 11/12] virtio_net: Add support for TCP and UDP ethtool rules
* [PATCH net-next v4 12/12] virtio_net: Add get ethtool flow rules ops
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/92d05cd4-4dd5-492f-abd1-f6642ecc0750
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 18a7e218cfcdca6666e1f7356533e4c988780b57
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/fdac0019-d488-4540-91f7-9dfd607d464e/config
drivers/virtio/virtio_pci_modern.c:326:26: error: no member named 'support_caps' in 'struct virtio_admin_cmd_query_cap_id_result'; did you mean 'supported_caps'?
***
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:
[alex.williamson@redhat.com andrew@lunn.ch danielj@nvidia.com edumazet@google.com eperezma@redhat.com jasowang@redhat.com jgg@ziepe.ca kevin.tian@intel.com kuba@kernel.org mst@redhat.com netdev@vger.kernel.org pabeni@redhat.com parav@nvidia.com shameerali.kolothum.thodi@huawei.com shshitrit@nvidia.com virtualization@lists.linux.dev xuanzhuo@linux.alibaba.com yohadt@nvidia.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-10-13 17:54 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=68ed3cec.050a0220.91a22.01e9.GAE@google.com \
--to=syzbot+ci454bc7cba78429ac@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.