linux-kernel - Re: linux-next: duplicate patches in the ipsec-next tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z/9uzypVKdsHwTCF@gauss3.secunet.de>
Date: Wed, 16 Apr 2025 10:48:15 +0200
From: Steffen Klassert <steffen.klassert@...unet.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "Linux Next
 Mailing List" <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the ipsec-next tree

On Tue, Apr 15, 2025 at 11:50:00AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in the ipsec tree as different commits
> (but the same patches):
> 
>   ee2fc517feba ("espintcp: remove encap socket caching to avoid reference leak")
>   4f1d804e288e ("espintcp: fix skb leaks")
> 
> These are commits
> 
>   028363685bd0 ("espintcp: remove encap socket caching to avoid reference leak")
>   63c1f19a3be3 ("espintcp: fix skb leaks")
> 
> in the ipsec tree.

They should have been just in the ipsec tree. I removed them from
ipsec-next. Sorry for this!