netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Nault <g.nault@alphalink.fr>
To: netdev@vger.kernel.org
Cc: James Chapman <jchapman@katalix.com>
Subject: [PATCH net-next 0/3] l2tp: avoid aliasing tunnels socket pointer
Date: Sat, 11 Nov 2017 06:06:23 +0900	[thread overview]
Message-ID: <cover.1510346873.git.g.nault@alphalink.fr> (raw)

We don't need to copy the tunnel's socket pointer in the pseudo-wire
specific session structures. This uselessly complicates the code
and hampers evolution.

This series was part of an effort to protect tunnels socket pointer
with RCU. But since it provides nice cleanup, I submit it separately.

Guillaume Nault (3):
  l2tp: remove .tunnel_sock from struct l2tp_eth
  l2tp: avoid using ->tunnel_sock for getting session's parent tunnel
  l2tp: remove the .tunnel_sock field from struct pppol2tp_session

 net/l2tp/l2tp_eth.c |  2 --
 net/l2tp/l2tp_ppp.c | 76 +++++++++--------------------------------------------
 2 files changed, 12 insertions(+), 66 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-11-10 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 21:06 Guillaume Nault [this message]
2017-11-10 21:06 ` [PATCH net-next 1/3] l2tp: remove .tunnel_sock from struct l2tp_eth Guillaume Nault
2017-11-10 21:06 ` [PATCH net-next 2/3] l2tp: avoid using ->tunnel_sock for getting session's parent tunnel Guillaume Nault
2017-11-10 21:06 ` [PATCH net-next 3/3] l2tp: remove the .tunnel_sock field from struct pppol2tp_session Guillaume Nault
2017-11-11 13:08 ` [PATCH net-next 0/3] l2tp: avoid aliasing tunnels socket pointer David Miller

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.1510346873.git.g.nault@alphalink.fr \
    --to=g.nault@alphalink.fr \
    --cc=jchapman@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;
as well as URLs for NNTP newsgroup(s).