All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Nault <g.nault@alphalink.fr>
To: netdev@vger.kernel.org
Cc: James Chapman <jchapman@katalix.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: [PATCH 0/2] L2TP fixes
Date: Tue, 4 Mar 2014 22:24:54 +0100	[thread overview]
Message-ID: <cover.1393966618.git.g.nault@alphalink.fr> (raw)

Here's a small series, to fix some (probably not widely used) L2TPv2
features:
  -toggling L2TP sequencing option from userspace was broken because
   of missing header length update,
  -no data was ever returned to userspace when reading from L2TP
   sockets, because pppol2tp_recv() did only handle the case of
   L2TP sockets bound to a PPP channel.

Guillaume Nault (2):
  l2tp: fix manual sequencing (de)activation in L2TPv2
  l2tp: fix userspace reception on plain L2TP sockets

 net/l2tp/l2tp_core.c    |  5 +++--
 net/l2tp/l2tp_core.h    |  1 +
 net/l2tp/l2tp_netlink.c |  4 +++-
 net/l2tp/l2tp_ppp.c     | 13 ++++++++-----
 4 files changed, 15 insertions(+), 8 deletions(-)

-- 
1.9.0

             reply	other threads:[~2014-03-04 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 21:24 Guillaume Nault [this message]
2014-03-04 21:25 ` [PATCH 1/2] l2tp: fix manual sequencing (de)activation in L2TPv2 Guillaume Nault
2014-03-06  1:39   ` David Miller
2014-03-04 21:25 ` [PATCH 2/2] l2tp: fix userspace reception on plain L2TP sockets Guillaume Nault
2014-03-04 21:38 ` [PATCH net 0/2] L2TP fixes Guillaume Nault
2014-03-05  7:23 ` [PATCH " James Chapman
2014-03-06 10:14 ` [PATCHv2 net 1/2] l2tp: fix manual sequencing (de)activation in L2TPv2 Guillaume Nault
2014-03-06 19:26   ` David Miller
2014-03-06 10:15 ` [PATCHv2 net 2/2] l2tp: fix userspace reception on plain L2TP sockets Guillaume Nault
2014-03-06 19:26   ` 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.1393966618.git.g.nault@alphalink.fr \
    --to=g.nault@alphalink.fr \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.