From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Gal Pressman <gal@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>, <netdev@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>, Simon Horman <horms@kernel.org>,
Shuah Khan <shuah@kernel.org>, Joe Damato <jdamato@fastly.com>,
<linux-kselftest@vger.kernel.org>,
Tariq Toukan <tariqt@nvidia.com>, Nimrod Oren <noren@nvidia.com>
Subject: Re: [PATCH net v2 1/2] net: ethtool: Don't check if RSS context exists in case of context 0
Date: Mon, 9 Jun 2025 15:38:12 +0000 [thread overview]
Message-ID: <aEb_5C9eDYVSkMHn@64799e4f873a> (raw)
In-Reply-To: <20250609120250.1630125-2-gal@nvidia.com>
On 2025-06-09 at 12:02:49, Gal Pressman (gal@nvidia.com) wrote:
> Context 0 (default context) always exists, there is no need to check
> whether it exists or not when adding a flow steering rule.
>
> The existing check fails when creating a flow steering rule for context
> 0 as it is not stored in the rss_ctx xarray.
>
> For example:
> $ ethtool --config-ntuple eth2 flow-type tcp4 dst-ip 194.237.147.23 dst-port 19983 context 0 loc 618
> rmgr: Cannot insert RX class rule: Invalid argument
> Cannot insert classification rule
>
> An example usecase for this could be:
> - A high-priority rule (loc 0) directing specific port traffic to
> context 0.
> - A low-priority rule (loc 1) directing all other TCP traffic to context
> 1.
>
> Fixes: de7f7582dff2 ("net: ethtool: prevent flow steering to RSS contexts which don't exist")
> Cc: Jakub Kicinski <kuba@kernel.org>
> Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
> Reviewed-by: Nimrod Oren <noren@nvidia.com>
> Signed-off-by: Gal Pressman <gal@nvidia.com>
> Reviewed-by: Joe Damato <jdamato@fastly.com>
Reviewed-by: Subbaraya Sundeep <sbhatta@marvell.com>
Thanks,
Sundeep
> ---
> net/ethtool/ioctl.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/ethtool/ioctl.c b/net/ethtool/ioctl.c
> index 39ec920f5de7..71c828d0bf31 100644
> --- a/net/ethtool/ioctl.c
> +++ b/net/ethtool/ioctl.c
> @@ -1083,7 +1083,8 @@ static noinline_for_stack int ethtool_set_rxnfc(struct net_device *dev,
> ethtool_get_flow_spec_ring(info.fs.ring_cookie))
> return -EINVAL;
>
> - if (!xa_load(&dev->ethtool->rss_ctx, info.rss_context))
> + if (info.rss_context &&
> + !xa_load(&dev->ethtool->rss_ctx, info.rss_context))
> return -EINVAL;
> }
>
> --
> 2.40.1
>
next prev parent reply other threads:[~2025-06-09 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 12:02 [PATCH net v2 0/2] Fix ntuple rules targeting default RSS Gal Pressman
2025-06-09 12:02 ` [PATCH net v2 1/2] net: ethtool: Don't check if RSS context exists in case of context 0 Gal Pressman
2025-06-09 15:38 ` Subbaraya Sundeep [this message]
2025-06-09 22:41 ` Jakub Kicinski
2025-06-10 5:58 ` Gal Pressman
2025-06-10 21:33 ` Jakub Kicinski
2025-06-09 12:02 ` [PATCH net v2 2/2] selftests: drv-net: rss_ctx: Add test for ntuple rules targeting default RSS context Gal Pressman
2025-06-10 21:32 ` Jakub Kicinski
2025-06-11 5:06 ` Gal Pressman
2025-06-11 15:52 ` Jakub Kicinski
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=aEb_5C9eDYVSkMHn@64799e4f873a \
--to=sbhatta@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=tariqt@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).