All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Paolo Abeni <pabeni@redhat.com>, Raed Salem <raeds@nvidia.com>
Subject: [PATCH xfrm 0/2] Couple of error unwind fixes to packet offload
Date: Wed, 19 Apr 2023 15:19:06 +0300	[thread overview]
Message-ID: <cover.1681906552.git.leon@kernel.org> (raw)

From: Leon Romanovsky <leonro@nvidia.com>

Hi Steffen,

There are two straightforward fixes to XFRM.

Thanks

Leon Romanovsky (2):
  xfrm: release all offloaded policy memory
  xfrm: Fix leak of dev tracker

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

-- 
2.40.0


             reply	other threads:[~2023-04-19 12:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 12:19 Leon Romanovsky [this message]
2023-04-19 12:19 ` [PATCH xfrm 1/2] xfrm: release all offloaded policy memory Leon Romanovsky
2023-04-20 15:10   ` Simon Horman
2023-04-20 16:51   ` Eric Dumazet
2023-04-20 17:04     ` Leon Romanovsky
2023-04-20 17:33       ` Eric Dumazet
2023-04-21  8:46         ` Steffen Klassert
2023-04-19 12:19 ` [PATCH xfrm 2/2] xfrm: Fix leak of dev tracker Leon Romanovsky
2023-04-20 15:10   ` Simon Horman
2023-04-20 16:44   ` Eric Dumazet
2023-04-21  8:45 ` [PATCH xfrm 0/2] Couple of error unwind fixes to packet offload 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=cover.1681906552.git.leon@kernel.org \
    --to=leon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=raeds@nvidia.com \
    --cc=steffen.klassert@secunet.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 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.