Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mark Bloch <mbloch@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch, saeedm@nvidia.com,
	tariqt@nvidia.com, leon@kernel.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net/mlx5: HWS, Improve IP version handling
Date: Thu, 24 Apr 2025 02:00:39 +0000	[thread overview]
Message-ID: <174546003948.2831734.1789243432503891447.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250422092540.182091-1-mbloch@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 22 Apr 2025 12:25:37 +0300 you wrote:
> This small series hardens our checks against a single matcher containing
> rules that match on IPv4 and IPv6. This scenario is not supported by
> hardware steering and the implementation now signals this instead of
> failing silently.
> 
> Patches:
> * Patch 1 forbids a single definer to match on mixed IP versions for
>   source and destination address.
> * Patch 2 reproduces a couple of firmware checks: it forbids creating
>   a definer that matches on IP address without matching on IP version,
>   and also disallows matching on IPv6 addresses and the IPv4 IHL fields
>   in the same definer.
> * Patch 3 forbids mixing rules that match on IPv4 and IPv6 addresses in
>   the same matcher. The underlying definer mechanism does not support
>   that.
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] net/mlx5: HWS, Fix IP version decision
    https://git.kernel.org/netdev/net-next/c/5f2f8d8b6800
  - [net-next,2/3] net/mlx5: HWS, Harden IP version definer checks
    https://git.kernel.org/netdev/net-next/c/6991a975e416
  - [net-next,3/3] net/mlx5: HWS, Disallow matcher IP version mixing
    https://git.kernel.org/netdev/net-next/c/f41f3edf0b15

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-04-24  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  9:25 [PATCH net-next 0/3] net/mlx5: HWS, Improve IP version handling Mark Bloch
2025-04-22  9:25 ` [PATCH net-next 1/3] net/mlx5: HWS, Fix IP version decision Mark Bloch
2025-04-22  9:25 ` [PATCH net-next 2/3] net/mlx5: HWS, Harden IP version definer checks Mark Bloch
2025-04-22  9:25 ` [PATCH net-next 3/3] net/mlx5: HWS, Disallow matcher IP version mixing Mark Bloch
2025-04-24  2:00 ` patchwork-bot+netdevbpf [this message]

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=174546003948.2831734.1789243432503891447.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --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