Netdev List
 help / color / mirror / Atom feed
From: Tom Parkin <tparkin@katalix.com>
To: netdev@vger.kernel.org
Cc: Tom Parkin <tparkin@katalix.com>
Subject: [PATCH 0/4] l2tp: fix up network namespace use in l2tp_core
Date: Wed,  9 Jan 2013 18:36:19 +0000	[thread overview]
Message-ID: <1357756583-22535-1-git-send-email-tparkin@katalix.com> (raw)

This patchset addresses network namespace issues in l2tp_core as previously
raised on netdev[1].

There is further work to be done to bring namespace support to the rest of
l2tp -- this will be addressed in a further patchset.

I've tested these changes using a stress script based around iproute2's netns
command.  Test platforms include i386, x86_64, and armv6l, running on
single-core and SMP platforms, and with/without preemption enabled.

[1].
http://www.spinics.net/lists/netdev/msg214776.html
http://www.spinics.net/lists/netdev/msg212234.html

Tom Parkin (4):
  l2tp: set netnsok flag for netlink messages
  l2tp: prevent tunnel creation on netns mismatch
  l2tp: don't pin network namespaces with tunnel sockets
  l2tp: clear tunnel socket field as soon as we release it

 net/l2tp/l2tp_core.c    |  101 +++++++++++++++++++++++++++++++----------------
 net/l2tp/l2tp_netlink.c |    1 +
 2 files changed, 68 insertions(+), 34 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2013-01-09 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 18:36 Tom Parkin [this message]
2013-01-09 18:36 ` [PATCH 1/4] l2tp: set netnsok flag for netlink messages Tom Parkin
2013-01-09 18:36 ` [PATCH 2/4] l2tp: prevent tunnel creation on netns mismatch Tom Parkin
2013-01-09 18:36 ` [PATCH 3/4] l2tp: don't pin network namespaces with tunnel sockets Tom Parkin
2013-01-09 18:36 ` [PATCH 4/4] l2tp: clear tunnel socket field as soon as we release it Tom Parkin
2013-01-10 16:48 ` [PATCH 0/4] l2tp: fix up network namespace use in l2tp_core Tom Parkin

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=1357756583-22535-1-git-send-email-tparkin@katalix.com \
    --to=tparkin@katalix.com \
    --cc=netdev@vger.kernel.org \
    /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