netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: netdev@vger.kernel.org
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
	"David S. Miller" <davem@davemloft.net>,
	Sabrina Dubroca <sd@queasysnail.net>
Subject: [PATCH ipsec-next 0/3] xfrm: not register one xfrm(6)_tunnel object twice
Date: Mon, 13 Jul 2020 15:42:35 +0800	[thread overview]
Message-ID: <cover.1594625993.git.lucien.xin@gmail.com> (raw)

Now in ip(6)_vti and xfrm interface tunnel support, it uses the
same xfrm(6)_tunnel object to handle for AF_NET and AF_INET6 by
registering it twice.

However the xfrm(6)_tunnel object is linked into a list with its
'next' pointer. The second registering will cause its 'next'
pointer to be overwritten, and break the list.

So this patchset is to add a new xfrm(6)_tunnel object for each
of them and register it, although its members are the same with
the old one.

Xin Long (3):
  ip_vti: not register vti_ipip_handler twice
  ip6_vti: not register vti_ipv6_handler twice
  xfrm: interface: not xfrmi_ipv6/ipip_handler twice

 net/ipv4/ip_vti.c         | 13 ++++++++++---
 net/ipv6/ip6_vti.c        | 13 ++++++++++---
 net/xfrm/xfrm_interface.c | 22 ++++++++++++++++++----
 3 files changed, 38 insertions(+), 10 deletions(-)

-- 
2.1.0


             reply	other threads:[~2020-07-13  7:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  7:42 Xin Long [this message]
2020-07-13  7:42 ` [PATCH ipsec-next 1/3] ip_vti: not register vti_ipip_handler twice Xin Long
2020-07-13  7:42 ` [PATCH ipsec-next 2/3] ip6_vti: not register vti_ipv6_handler twice Xin Long
2020-07-13  7:42 ` [PATCH ipsec-next 3/3] xfrm: interface: not xfrmi_ipv6/ipip_handler twice Xin Long
2020-07-16  6:32 ` [PATCH ipsec-next 0/3] xfrm: not register one xfrm(6)_tunnel object twice 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=cover.1594625993.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    --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).