From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: xfrmi: request for stable trees
Date: Tue, 3 Dec 2019 16:50:51 +0100 [thread overview]
Message-ID: <95ca675f-3581-2784-c77d-95f2995ea3d7@6wind.com> (raw)
In-Reply-To: <20191203130345.GC8621@gauss3.secunet.de>
Le 03/12/2019 à 14:03, Steffen Klassert a écrit :
> 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")
>
> Nicolas,
>
> I'm currently processing the stable queue for v4.19.
> I guess we also need this patch from you:
>
> 56c5ee1a5823 ("xfrm interface: fix memory leak on creation")
>
> before we apply the above mentioned patches, right?
>
Right, I point it in my first email but I get an email from Sasha Levin the 25th
October:
[PATCH AUTOSEL 4.19 16/37] xfrm interface: fix memory leak on creation
so I was thinking that it is already queued. But I can't see it in linux-stable.
prev parent reply other threads:[~2019-12-03 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 10:21 pull request (net): ipsec 2019-09-05 Steffen Klassert
2019-09-05 10:21 ` [PATCH 1/5] xfrm interface: avoid corruption on changelink Steffen Klassert
2019-09-05 10:21 ` [PATCH 2/5] xfrm interface: ifname may be wrong in logs Steffen Klassert
2019-09-05 10:21 ` [PATCH 3/5] xfrm interface: fix list corruption for x-netns Steffen Klassert
2019-09-05 10:22 ` [PATCH 4/5] xfrm interface: fix management of phydev Steffen Klassert
2019-09-05 10:22 ` [PATCH 5/5] xfrm: policy: avoid warning splat when merging nodes Steffen Klassert
2019-09-06 13:09 ` pull request (net): ipsec 2019-09-05 David Miller
2019-10-14 9:31 ` Nicolas Dichtel
2019-11-18 15:31 ` xfrmi: request for stable trees (was: Re: pull request (net): ipsec 2019-09-05) Nicolas Dichtel
2019-11-24 10:07 ` Steffen Klassert
2019-11-25 3:02 ` xfrmi: request for stable trees David Miller
2019-11-26 8:12 ` Steffen Klassert
2019-11-27 8:33 ` Nicolas Dichtel
2019-12-03 13:03 ` xfrmi: request for stable trees (was: Re: pull request (net): ipsec 2019-09-05) Steffen Klassert
2019-12-03 15:50 ` Nicolas Dichtel [this message]
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=95ca675f-3581-2784-c77d-95f2995ea3d7@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--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).