From: Simon Horman <horms@kernel.org>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH ipsec 1/2] espintcp: fix skb leaks
Date: Fri, 11 Apr 2025 14:58:44 +0100 [thread overview]
Message-ID: <20250411135844.GF395307@horms.kernel.org> (raw)
In-Reply-To: <66e251a2e391e15a62c1026761e2076accf55db0.1744206087.git.sd@queasysnail.net>
On Wed, Apr 09, 2025 at 03:59:56PM +0200, Sabrina Dubroca wrote:
> A few error paths are missing a kfree_skb.
>
> Fixes: e27cca96cd68 ("xfrm: add espintcp (RFC 8229)")
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-04-11 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 13:59 [PATCH ipsec 0/2] fix some leaks in espintcp Sabrina Dubroca
2025-04-09 13:59 ` [PATCH ipsec 1/2] espintcp: fix skb leaks Sabrina Dubroca
2025-04-11 13:58 ` Simon Horman [this message]
2025-04-09 13:59 ` [PATCH ipsec 2/2] espintcp: remove encap socket caching to avoid reference leak Sabrina Dubroca
2025-04-11 13:59 ` Simon Horman
2025-04-14 10:00 ` [PATCH ipsec 0/2] fix some leaks in espintcp 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=20250411135844.GF395307@horms.kernel.org \
--to=horms@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--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 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).