From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Steffen Klassert <steffen.klassert@secunet.com>,
David Miller <davem@davemloft.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, netdev@vger.kernel.org
Subject: Re: pull request (net): ipsec 2019-09-05
Date: Mon, 14 Oct 2019 11:31:47 +0200 [thread overview]
Message-ID: <3a94c153-c8f1-45d1-9f0d-68ca5b83b44c@6wind.com> (raw)
In-Reply-To: <20190905102201.1636-1-steffen.klassert@secunet.com>
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?
And also 56c5ee1a5823 ("xfrm interface: fix memory leak on creation")?
Thank you,
Nicolas
>
> 2) Fix a potential warning when merging xfrm_plocy nodes.
> From Florian Westphal.
>
> Please pull or let me know if there are problems.
>
> Thanks!
>
> The following changes since commit 114a5c3240155fdb01bf821c9d326d7bb05bd464:
>
> Merge tag 'mlx5-fixes-2019-07-11' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux (2019-07-11 15:06:37 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git master
>
> for you to fetch changes up to 769a807d0b41df4201dbeb01c22eaeb3e5905532:
>
> xfrm: policy: avoid warning splat when merging nodes (2019-08-20 08:09:42 +0200)
>
> ----------------------------------------------------------------
> Florian Westphal (1):
> xfrm: policy: avoid warning splat when merging nodes
>
> Nicolas Dichtel (4):
> xfrm interface: avoid corruption on changelink
> xfrm interface: ifname may be wrong in logs
> xfrm interface: fix list corruption for x-netns
> xfrm interface: fix management of phydev
>
> include/net/xfrm.h | 2 --
> net/xfrm/xfrm_interface.c | 56 +++++++++++++-----------------
> net/xfrm/xfrm_policy.c | 6 ++--
> tools/testing/selftests/net/xfrm_policy.sh | 7 ++++
> 4 files changed, 36 insertions(+), 35 deletions(-)
>
next prev parent reply other threads:[~2019-10-14 9:31 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 [this message]
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 ` xfrmi: request for stable trees Nicolas Dichtel
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=3a94c153-c8f1-45d1-9f0d-68ca5b83b44c@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.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).