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>, <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/12] pull request (net-next): ipsec-next 2025-05-23
Date: Fri, 23 May 2025 12:36:02 +0200	[thread overview]
Message-ID: <aDBPkpKv+x7YFDWJ@gauss3.secunet.de> (raw)
In-Reply-To: <20250523075611.3723340-1-steffen.klassert@secunet.com>

On Fri, May 23, 2025 at 09:55:59AM +0200, Steffen Klassert wrote:
> 1) Remove some unnecessary strscpy_pad() size arguments.
>    From Thorsten Blum.
> 
> 2) Correct use of xso.real_dev on bonding offloads.
>    Patchset from Cosmin Ratiu.
> 
> 3) Add hardware offload configuration to XFRM_MSG_MIGRATE.
>    From Chiachang Wang.
> 
> 4) Refactor migration setup during cloning. This was
>    done after the clone was created. Now it is done
>    in the cloning function itself.
>    From Chiachang Wang.
> 
> 5) Validate assignment of maximal possible SEQ number.
>    Prevent from setting to the maximum sequrnce number
>    as this would cause for traffic drop.
>    From Leon Romanovsky.
> 
> 6) Prevent configuration of interface index when offload
>    is used. Hardware can't handle this case.i
>    From Leon Romanovsky.
> 
> 7) Always use kfree_sensitive() for SA secret zeroization.
>    From Zilin Guan.
> 
> Please pull or let me know if there are problems.
> 
> Thanks!

I forgot to mention a merge conflict between

 fd5ef5203ce6 ("ixgbe: wrap netdev_priv() usage")

from the net-next tree and commit:

  43eca05b6a3b ("xfrm: Add explicit dev to .xdo_dev_state_{add,delete,free}")

from the ipsec-next tree.

It can be solved as done in linux-next.

Thanks!

      parent reply	other threads:[~2025-05-23 10:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23  7:55 [PATCH 0/12] pull request (net-next): ipsec-next 2025-05-23 Steffen Klassert
2025-05-23  7:56 ` [PATCH 01/12] xfrm: Remove unnecessary strscpy_pad() size arguments Steffen Klassert
2025-05-26 16:50   ` patchwork-bot+netdevbpf
2025-05-23  7:56 ` [PATCH 02/12] net/mlx5: Avoid using xso.real_dev unnecessarily Steffen Klassert
2025-05-23  7:56 ` [PATCH 03/12] xfrm: Use xdo.dev instead of xdo.real_dev Steffen Klassert
2025-05-23  7:56 ` [PATCH 04/12] xfrm: Remove unneeded device check from validate_xmit_xfrm Steffen Klassert
2025-05-23  7:56 ` [PATCH 05/12] xfrm: Add explicit dev to .xdo_dev_state_{add,delete,free} Steffen Klassert
2025-05-23  7:56 ` [PATCH 06/12] bonding: Mark active offloaded xfrm_states Steffen Klassert
2025-05-23  7:56 ` [PATCH 07/12] bonding: Fix multiple long standing offload races Steffen Klassert
2025-05-23  7:56 ` [PATCH 08/12] xfrm: Migrate offload configuration Steffen Klassert
2025-05-23  7:56 ` [PATCH 09/12] xfrm: Refactor migration setup during the cloning process Steffen Klassert
2025-05-23  7:56 ` [PATCH 10/12] xfrm: validate assignment of maximal possible SEQ number Steffen Klassert
2025-05-23  7:56 ` [PATCH 11/12] xfrm: prevent configuration of interface index when offload is used Steffen Klassert
2025-05-23  7:56 ` [PATCH 12/12] xfrm: use kfree_sensitive() for SA secret zeroization Steffen Klassert
2025-05-23 10:36 ` Steffen Klassert [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=aDBPkpKv+x7YFDWJ@gauss3.secunet.de \
    --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.