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>, Chris Elston <celston@katalix.com>
Subject: [PATCH net 0/2] l2tp: socket lookup fixes for l2tp_ip and l2tp_ip6
Date: Fri, 30 Dec 2016 19:48:17 +0100	[thread overview]
Message-ID: <cover.1483123297.git.g.nault@alphalink.fr> (raw)

There are still some cases that aren't correctly handled in the socket
lookup functions of l2tp_ip and l2tp_ip6. This series fixes lookups for
connected sockets and for sockets bound to the IPv6 unspecified
address.

bind() and connect() should now work as expected on IPPROTO_L2TP
sockets. Extra features, like SO_REUSEADDR, remain unsupported.

The matching conditions in __l2tp_ip6_bind_lookup() and
__l2tp_ip_bind_lookup() are getting hard to read. I've kept the single
test approach to make the intend of the patches clear. I'll split the
conditionals once these fixes reach net-next.


Guillaume Nault (2):
  l2tp: consider '::' as wildcard address in l2tp_ip6 socket lookup
  l2tp: take remote address into account in l2tp_ip and l2tp_ip6 socket
    lookups

 net/l2tp/l2tp_ip.c  | 19 ++++++-------------
 net/l2tp/l2tp_ip6.c | 24 ++++++++----------------
 2 files changed, 14 insertions(+), 29 deletions(-)

-- 
2.11.0

             reply	other threads:[~2016-12-30 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30 18:48 Guillaume Nault [this message]
2016-12-30 18:48 ` [PATCH net 1/2] l2tp: consider '::' as wildcard address in l2tp_ip6 socket lookup Guillaume Nault
2016-12-30 18:48 ` [PATCH net 2/2] l2tp: take remote address into account in l2tp_ip and l2tp_ip6 socket lookups Guillaume Nault
2017-01-02  3:07 ` [PATCH net 0/2] l2tp: socket lookup fixes for l2tp_ip and l2tp_ip6 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.1483123297.git.g.nault@alphalink.fr \
    --to=g.nault@alphalink.fr \
    --cc=celston@katalix.com \
    --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).