All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Rastislav Szabo <rastislav.szabo@isovalent.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, davem@davemloft.net,
	dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	shuah@kernel.org, dima@arista.com,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 1/2] net/tcp: fix TCP-AO key deletion in VRFs
Date: Thu, 27 Aug 2026 10:10:06 +0000	[thread overview]
Message-ID: <178782540674.1145855.8291296014675389448.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260822201119.272269-1-rastislav.szabo@isovalent.com>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sat, 22 Aug 2026 22:11:18 +0200 you wrote:
> TCP-AO keys with TCP_AO_KEYF_IFINDEX store the VRF L3 interface index in
> l3index. tcp_ao_del_cmd() validates the supplied ifindex, but does not
> assign it to its local l3index before matching keys.
> 
> As a result, deleting a key scoped to a non-default VRF always fails with
> ENOENT because it is matched against l3index 0.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/2] net/tcp: fix TCP-AO key deletion in VRFs
    https://git.kernel.org/netdev/net/c/94ad9e114a1c
  - [net,v2,2/2] selftests: net: tcp_ao: test VRF-scoped key deletion
    https://git.kernel.org/netdev/net/c/687e5b48c4f5

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



      parent reply	other threads:[~2026-08-27 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 20:11 [PATCH net v2 1/2] net/tcp: fix TCP-AO key deletion in VRFs Rastislav Szabo
2026-08-22 20:11 ` [PATCH net v2 2/2] selftests: net: tcp_ao: test VRF-scoped key deletion Rastislav Szabo
2026-08-27 10:10 ` 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=178782540674.1145855.8291296014675389448.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dima@arista.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rastislav.szabo@isovalent.com \
    --cc=shuah@kernel.org \
    /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.