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/5] l2tp: fixes for l2tp_ip and l2tp_ip6 socket handling
Date: Mon, 28 Nov 2016 20:39:54 +0100 [thread overview]
Message-ID: <cover.1480360512.git.g.nault@alphalink.fr> (raw)
This series addresses problems found while working on commit 32c231164b76
("l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind()").
The first three patches fix races in socket's connect, recv and bind
operations. The last two ones fix scenarios where l2tp fails to
correctly lookup its userspace sockets.
Apart from the last patch, which is l2tp_ip6 specific, every patch fixes
the same problem in the L2TP IPv4 and IPv6 code.
Guillaume Nault (5):
l2tp: lock socket before checking flags in connect()
l2tp: hold socket before dropping lock in l2tp_ip{,6}_recv()
l2tp: fix racy socket lookup in l2tp_ip and l2tp_ip6 bind()
l2tp: fix lookup for sockets not bound to a device in l2tp_ip
l2tp: fix address test in __l2tp_ip6_bind_lookup()
include/net/ipv6.h | 2 ++
net/ipv6/datagram.c | 4 ++-
net/l2tp/l2tp_ip.c | 61 +++++++++++++++++++++--------------------
net/l2tp/l2tp_ip6.c | 79 ++++++++++++++++++++++++++++-------------------------
4 files changed, 79 insertions(+), 67 deletions(-)
--
2.10.2
next reply other threads:[~2016-11-28 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 19:39 Guillaume Nault [this message]
2016-11-28 19:39 ` [PATCH net 1/5] l2tp: lock socket before checking flags in connect() Guillaume Nault
2016-11-28 19:39 ` [PATCH net 2/5] l2tp: hold socket before dropping lock in l2tp_ip{,6}_recv() Guillaume Nault
2016-11-28 19:39 ` [PATCH net 3/5] l2tp: fix racy socket lookup in l2tp_ip and l2tp_ip6 bind() Guillaume Nault
2016-11-28 21:10 ` kbuild test robot
2016-11-29 12:12 ` Guillaume Nault
2016-11-28 19:40 ` [PATCH net 4/5] l2tp: fix lookup for sockets not bound to a device in l2tp_ip Guillaume Nault
2016-11-28 19:40 ` [PATCH net 5/5] l2tp: fix address test in __l2tp_ip6_bind_lookup() Guillaume Nault
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.1480360512.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).