From: Simon Horman <horms@kernel.org>
To: Daniel Jurgens <danielj@nvidia.com>
Cc: netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
pabeni@redhat.com, virtualization@lists.linux.dev,
parav@nvidia.com, shshitrit@nvidia.com, yohadt@nvidia.com,
xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
shameerali.kolothum.thodi@huawei.com, jgg@ziepe.ca,
kevin.tian@intel.com, kuba@kernel.org, andrew+netdev@lunn.ch,
edumazet@google.com
Subject: Re: [PATCH net-next v10 07/12] virtio_net: Implement layer 2 ethtool flow rules
Date: Mon, 17 Nov 2025 17:15:50 +0000 [thread overview]
Message-ID: <aRtYRhKK8lbvREcy@horms.kernel.org> (raw)
In-Reply-To: <20251112193435.2096-8-danielj@nvidia.com>
On Wed, Nov 12, 2025 at 01:34:30PM -0600, Daniel Jurgens wrote:
...
> +static int setup_classifier(struct virtnet_ff *ff, struct virtnet_classifier *c)
> +{
> + int err;
> +
> + err = xa_alloc(&ff->classifiers, &c->id, c,
> + XA_LIMIT(0, le32_to_cpu(ff->ff_caps->classifiers_limit) - 1),
> + GFP_KERNEL);
Hi Daniel,
I am wondering if some sort of bounds checking should be done for
classifiers_limit. E.g. if it is 0, then this will set the
maximum limit to -1 (UINT_MAX), which seems somewhat large,
assuming classifiers_limit of 0 doesn't mean unlimited.
Flagged by Claude Code with https://github.com/masoncl/review-prompts/
> + if (err)
> + return err;
> +
> + err = virtio_admin_obj_create(ff->vdev,
> + VIRTIO_NET_RESOURCE_OBJ_FF_CLASSIFIER,
> + c->id,
> + VIRTIO_ADMIN_GROUP_TYPE_SELF,
> + 0,
> + &c->classifier,
> + c->size);
> + if (err)
> + goto err_xarray;
> +
> + return 0;
> +
> +err_xarray:
> + xa_erase(&ff->classifiers, c->id);
> +
> + return err;
> +}
...
> +static int virtnet_ethtool_flow_insert(struct virtnet_ff *ff,
> + struct ethtool_rx_flow_spec *fs,
> + u16 curr_queue_pairs)
> +{
> + struct virtnet_ethtool_rule *eth_rule;
> + int err;
> +
> + if (!ff->ff_supported)
> + return -EOPNOTSUPP;
> +
> + err = validate_flow_input(ff, fs, curr_queue_pairs);
> + if (err)
> + return err;
> +
> + eth_rule = kzalloc(sizeof(*eth_rule), GFP_KERNEL);
> + if (!eth_rule)
> + return -ENOMEM;
> +
> + err = xa_alloc(&ff->ethtool.rules, &fs->location, eth_rule,
> + XA_LIMIT(0, le32_to_cpu(ff->ff_caps->rules_limit) - 1),
> + GFP_KERNEL);
Likewise for rules_limit.
> + if (err)
> + goto err_rule;
> +
> + eth_rule->flow_spec = *fs;
> +
> + err = build_and_insert(ff, eth_rule);
> + if (err)
> + goto err_xa;
> +
> + return err;
> +
> +err_xa:
> + xa_erase(&ff->ethtool.rules, eth_rule->flow_spec.location);
> +
> +err_rule:
> + fs->location = RX_CLS_LOC_ANY;
> + kfree(eth_rule);
> +
> + return err;
> +}
...
next prev parent reply other threads:[~2025-11-17 17:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 19:34 [PATCH net-next v10 01/12] virtio_pci: Remove supported_cap size build assert Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 02/12] virtio: Add config_op for admin commands Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 03/12] virtio: Expose generic device capability operations Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 04/12] virtio: Expose object create and destroy API Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 05/12] virtio_net: Query and set flow filter caps Daniel Jurgens
2025-11-17 17:16 ` Simon Horman
2025-11-17 17:49 ` Dan Jurgens
2025-11-17 21:18 ` Simon Horman
2025-11-17 21:21 ` Dan Jurgens
2025-11-18 9:45 ` Simon Horman
2025-11-12 19:34 ` [PATCH net-next v10 06/12] virtio_net: Create a FF group for ethtool steering Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 07/12] virtio_net: Implement layer 2 ethtool flow rules Daniel Jurgens
2025-11-17 17:15 ` Simon Horman [this message]
2025-11-12 19:34 ` [PATCH net-next v10 08/12] virtio_net: Use existing classifier if possible Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 09/12] virtio_net: Implement IPv4 ethtool flow rules Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 10/12] virtio_net: Add support for IPv6 ethtool steering Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 11/12] virtio_net: Add support for TCP and UDP ethtool rules Daniel Jurgens
2025-11-12 19:34 ` [PATCH net-next v10 12/12] virtio_net: Add get ethtool flow rules ops Daniel Jurgens
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=aRtYRhKK8lbvREcy@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danielj@nvidia.com \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shshitrit@nvidia.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yohadt@nvidia.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;
as well as URLs for NNTP newsgroup(s).