netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Chentian Liu <chengtian.liu@corigine.com>,
	Huanhuan Wang <huanhuan.wang@corigine.com>,
	Yinjun Zhang <yinjun.zhang@corigine.com>,
	Louis Peens <louis.peens@corigine.com>,
	netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH net-next v3 2/3] nfp: add framework to support ipsec offloading
Date: Sun, 6 Nov 2022 21:39:51 +0200	[thread overview]
Message-ID: <Y2gNh3QvaK7MX9pp@unreal> (raw)
In-Reply-To: <20221101110248.423966-3-simon.horman@corigine.com>

On Tue, Nov 01, 2022 at 12:02:47PM +0100, Simon Horman wrote:
> From: Huanhuan Wang <huanhuan.wang@corigine.com>
> 
> A new metadata type and config structure are introduced to
> interact with firmware to support ipsec offloading. This
> feature relies on specific firmware that supports ipsec
> encrypt/decrypt by advertising related capability bit.
> 
> The xfrm callbacks which interact with upper layer are
> implemented in the following patch.
> 
> Based on initial work of Norm Bagley <norman.bagley@netronome.com>.
> 
> Signed-off-by: Huanhuan Wang <huanhuan.wang@corigine.com>
> Reviewed-by: Louis Peens <louis.peens@corigine.com>
> Signed-off-by: Simon Horman <simon.horman@corigine.com>
> ---
>  drivers/net/ethernet/netronome/Kconfig        |  11 ++
>  drivers/net/ethernet/netronome/nfp/Makefile   |   2 +
>  .../ethernet/netronome/nfp/crypto/crypto.h    |  23 ++++
>  .../net/ethernet/netronome/nfp/crypto/ipsec.c | 105 ++++++++++++++++++
>  drivers/net/ethernet/netronome/nfp/nfd3/dp.c  |  58 ++++++++--
>  .../net/ethernet/netronome/nfp/nfd3/ipsec.c   |  18 +++
>  .../net/ethernet/netronome/nfp/nfd3/nfd3.h    |   8 ++
>  drivers/net/ethernet/netronome/nfp/nfp_net.h  |   9 ++
>  .../ethernet/netronome/nfp/nfp_net_common.c   |   3 +
>  .../net/ethernet/netronome/nfp/nfp_net_ctrl.h |   4 +
>  10 files changed, 231 insertions(+), 10 deletions(-)
>  create mode 100644 drivers/net/ethernet/netronome/nfp/crypto/ipsec.c
>  create mode 100644 drivers/net/ethernet/netronome/nfp/nfd3/ipsec.c

<...>

> +void nfp_net_ipsec_clean(struct nfp_net *nn)
> +{
> +	if (!(nn->cap_w1 & NFP_NET_CFG_CTRL_IPSEC))
> +		return;
> +	xa_destroy(&nn->xa_ipsec);

You shouldn't use xa_destroy() here as if you have entries in xa_ipsec,
you won't release them and leak memory without any warning. Most likely,
the WARN_ON(!xa_empty(&nn->xa_ipsec)) is what you want here.

The rest code is ok.

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

  reply	other threads:[~2022-11-06 19:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 11:02 [PATCH net-next v3 0/3] nfp: IPsec offload support Simon Horman
2022-11-01 11:02 ` [PATCH net-next v3 1/3] nfp: extend capability and control words Simon Horman
2022-11-06 19:39   ` Leon Romanovsky
2022-11-01 11:02 ` [PATCH net-next v3 2/3] nfp: add framework to support ipsec offloading Simon Horman
2022-11-06 19:39   ` Leon Romanovsky [this message]
2022-11-01 11:02 ` [PATCH net-next v3 3/3] nfp: implement xfrm callbacks and expose ipsec offload feature to upper layer Simon Horman
2022-11-06 19:48   ` Leon Romanovsky
2022-11-07  9:50     ` Yinjun Zhang
2022-11-07  6:14   ` Leon Romanovsky
2022-11-07  9:46     ` Yinjun Zhang
2022-11-07 12:40       ` Leon Romanovsky
2022-11-08  1:28         ` Yinjun Zhang
2022-11-08 18:42           ` Leon Romanovsky
2022-11-09  6:51             ` Yinjun Zhang
2022-11-09  6:58     ` Yinjun Zhang
2022-11-09  8:26       ` Leon Romanovsky
2022-11-09 12:09         ` Yinjun Zhang
2022-11-09 12:24           ` Leon Romanovsky
2022-11-04  3:48 ` [PATCH net-next v3 0/3] nfp: IPsec offload support Jakub Kicinski
2022-11-05 15:27   ` Steffen Klassert
2022-11-05 17:25   ` Leon Romanovsky

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=Y2gNh3QvaK7MX9pp@unreal \
    --to=leon@kernel.org \
    --cc=chengtian.liu@corigine.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=huanhuan.wang@corigine.com \
    --cc=kuba@kernel.org \
    --cc=louis.peens@corigine.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.com \
    --cc=steffen.klassert@secunet.com \
    --cc=yinjun.zhang@corigine.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).