All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	<netdev@vger.kernel.org>
Subject: [PATCH 0/2] pull request (net): ipsec 2025-09-22
Date: Mon, 22 Sep 2025 09:34:51 +0200	[thread overview]
Message-ID: <20250922073512.62703-1-steffen.klassert@secunet.com> (raw)

1) Fix 0 assignment for SPIs. 0 is not a valid SPI,
   it means no SPI assigned.

2) Fix offloading for inter address family tunnels.

Both fixes from Sabrina Dubroca.

Please pull or let me know if there are problems.

Thanks!

The following changes since commit 52565a935213cd6a8662ddb8efe5b4219343a25d:

  net: kcm: Fix race condition in kcm_unattach() (2025-08-13 18:18:33 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git tags/ipsec-2025-09-22

for you to fetch changes up to 91d8a53db2199eefc73ecf3682e0665ea6895696:

  xfrm: fix offloading of cross-family tunnels (2025-09-15 11:35:06 +0200)

----------------------------------------------------------------
ipsec-2025-09-22

----------------------------------------------------------------
Sabrina Dubroca (2):
      xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
      xfrm: fix offloading of cross-family tunnels

 net/xfrm/xfrm_device.c | 2 +-
 net/xfrm/xfrm_state.c  | 3 +++
 2 files changed, 4 insertions(+), 1 deletion(-)

             reply	other threads:[~2025-09-22  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22  7:34 Steffen Klassert [this message]
2025-09-22  7:34 ` [PATCH 1/2] xfrm: xfrm_alloc_spi shouldn't use 0 as SPI Steffen Klassert
2025-09-23  0:10   ` patchwork-bot+netdevbpf
2025-09-22  7:34 ` [PATCH 2/2] xfrm: fix offloading of cross-family tunnels Steffen Klassert

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=20250922073512.62703-1-steffen.klassert@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.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.