[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZlWqbN01WEtPtxW7@gauss3.secunet.de>
Date: Tue, 28 May 2024 11:57:00 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Hagar Hemdan <hagarhem@...zon.com>
CC: Norbert Manthey <nmanthey@...zon.de>, Herbert Xu
<herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>,
"David Ahern" <dsahern@...nel.org>, Eric Dumazet <edumazet@...gle.com>,
"Jakub Kicinski" <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Sabrina
Dubroca <sd@...asysnail.net>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] net: esp: cleanup esp_output_tail_tcp() in case of
unsupported ESPINTCP
On Sat, May 18, 2024 at 01:04:39PM +0000, Hagar Hemdan wrote:
> xmit() functions should consume skb or return error codes in error
> paths.
> When the configuration "CONFIG_INET_ESPINTCP" is not set, the
> implementation of the function "esp_output_tail_tcp" violates this rule.
> The function frees the skb and returns the error code.
> This change removes the kfree_skb from both functions, for both
> esp4 and esp6.
> WARN_ON is added because esp_output_tail_tcp() should never be called if
> CONFIG_INET_ESPINTCP is not set.
>
> This bug was discovered and resolved using Coverity Static Analysis
> Security Testing (SAST) by Synopsys, Inc.
>
> Fixes: e27cca96cd68 ("xfrm: add espintcp (RFC 8229)")
> Signed-off-by: Hagar Hemdan <hagarhem@...zon.com>
Patch applied, thanks a lot!
Powered by blists - more mailing lists