netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: steffen.klassert@secunet.com, davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH ipsec v2 0/4] xfrm interface: bugs fixes
Date: Mon, 15 Jul 2019 12:00:19 +0200	[thread overview]
Message-ID: <20190715100023.8475-1-nicolas.dichtel@6wind.com> (raw)
In-Reply-To: <df990564-819a-314f-dda6-aab58a2e7b6e@6wind.com>


Here is a bunch of bugs fixes. Some have been seen by code review and some when
playing with x-netns.
The details are in each patch.

v1 -> v2:
 - add patch #3 and #4

 include/net/xfrm.h        |  2 --
 net/xfrm/xfrm_interface.c | 56 +++++++++++++++++++++--------------------------
 2 files changed, 25 insertions(+), 33 deletions(-)

Regards,
Nicolas


  reply	other threads:[~2019-07-15 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  7:45 [PATCH ipsec 0/2] xfrm interface: bug fix on changelink Nicolas Dichtel
2019-07-10  7:45 ` [PATCH ipsec 1/2] xfrm interface: avoid corruption " Nicolas Dichtel
2019-07-10  7:45 ` [PATCH ipsec 2/2] xfrm interface: ifname may be wrong in logs Nicolas Dichtel
2019-07-15  9:52 ` [PATCH ipsec 0/2] xfrm interface: bug fix on changelink Nicolas Dichtel
2019-07-15 10:00   ` Nicolas Dichtel [this message]
2019-07-15 10:00     ` [PATCH ipsec v2 1/4] xfrm interface: avoid corruption " Nicolas Dichtel
2019-07-15 10:00     ` [PATCH ipsec v2 2/4] xfrm interface: ifname may be wrong in logs Nicolas Dichtel
2019-07-15 10:00     ` [PATCH ipsec v2 3/4] xfrm interface: fix list corruption for x-netns Nicolas Dichtel
2019-07-15 10:00     ` [PATCH ipsec v2 4/4] xfrm interface: fix management of phydev Nicolas Dichtel
2019-07-18  7:37     ` [PATCH ipsec v2 0/4] xfrm interface: bugs fixes Steffen Klassert

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=20190715100023.8475-1-nicolas.dichtel@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=davem@davemloft.net \
    --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).