netdev - Re: xfrmi: request for stable trees

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20191124.190249.1262907259702322148.davem@davemloft.net>
Date:   Sun, 24 Nov 2019 19:02:49 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     steffen.klassert@...unet.com
Cc:     nicolas.dichtel@...nd.com, herbert@...dor.apana.org.au,
        netdev@...r.kernel.org
Subject: Re: xfrmi: request for stable trees

From: Steffen Klassert <steffen.klassert@...unet.com>
Date: Sun, 24 Nov 2019 11:07:46 +0100

> On Mon, Nov 18, 2019 at 04:31:14PM +0100, Nicolas Dichtel wrote:
>> Le 14/10/2019 à 11:31, Nicolas Dichtel a écrit :
>> > Le 05/09/2019 à 12:21, Steffen Klassert a écrit :
>> >> 1) Several xfrm interface fixes from Nicolas Dichtel:
>> >>    - Avoid an interface ID corruption on changelink.
>> >>    - Fix wrong intterface names in the logs.
>> >>    - Fix a list corruption when changing network namespaces.
>> >>    - Fix unregistation of the underying phydev.
>> > Is it possible to queue those patches for the stable trees?
>> 
>> Is there a chance to get them in the 4.19 stable tree?
>> 
>> Here are the sha1:
>> e9e7e85d75f3 ("xfrm interface: avoid corruption on changelink")
>> e0aaa332e6a9 ("xfrm interface: ifname may be wrong in logs")
>> c5d1030f2300 ("xfrm interface: fix list corruption for x-netns")
>> 22d6552f827e ("xfrm interface: fix management of phydev")
> 
> I'm ok with this. David does the stable submitting for
> networking patches usually. So I guess he will pick them
> into his stable queue after the patches are mainline some
> time.

Steffen you can submit things directly to -stable for IPSEC if you
wish, and it would help me in this case.

Thanks!