From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, jchapman@katalix.com, g.nault@alphalink.fr
Subject: [PATCH v3 net-next 0/4] l2tp: set l2specific_len based on l2specific_type
Date: Tue, 16 Jan 2018 23:01:53 +0100 [thread overview]
Message-ID: <cover.1516138644.git.lorenzo.bianconi@redhat.com> (raw)
Do not rely on l2specific_len value provided by userspace but set sublayer
length according to l2specific_type.
Mark L2TP_ATTR_L2SPEC_LEN attribute as not used
Changes since v2:
- drop the patch related to a fix in the switch default case in
l2tp_nl_cmd_session_create()
- use L2SPECTYPE_NONE as default case in l2tp_get_l2specific_len()
Changes since v1:
- remove l2specific_len parameter
- add sanity check on l2specific_type provided by userspace
Lorenzo Bianconi (4):
l2tp: double-check l2specific_type provided by userspace
l2tp: remove l2specific_len dependency in l2tp_core
l2tp: remove l2specific_len configurable parameter
l2tp: mark L2TP_ATTR_L2SPEC_LEN as not used
include/uapi/linux/l2tp.h | 2 +-
net/l2tp/l2tp_core.c | 35 ++++++++++++++++-------------------
net/l2tp/l2tp_core.h | 13 +++++++++++--
net/l2tp/l2tp_debugfs.c | 2 +-
net/l2tp/l2tp_netlink.c | 15 +++++++++------
5 files changed, 38 insertions(+), 29 deletions(-)
--
2.13.6
next reply other threads:[~2018-01-16 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 22:01 Lorenzo Bianconi [this message]
2018-01-16 22:01 ` [PATCH v3 net-next 1/4] l2tp: double-check l2specific_type provided by userspace Lorenzo Bianconi
2018-01-16 22:01 ` [PATCH v3 net-next 2/4] l2tp: remove l2specific_len dependency in l2tp_core Lorenzo Bianconi
2018-01-16 22:01 ` [PATCH v3 net-next 3/4] l2tp: remove l2specific_len configurable parameter Lorenzo Bianconi
2018-01-16 22:01 ` [PATCH v3 net-next 4/4] l2tp: mark L2TP_ATTR_L2SPEC_LEN as not used Lorenzo Bianconi
2018-01-17 10:23 ` [PATCH v3 net-next 0/4] l2tp: set l2specific_len based on l2specific_type Guillaume Nault
2018-01-17 14:56 ` James Chapman
2018-01-19 20:03 ` 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.1516138644.git.lorenzo.bianconi@redhat.com \
--to=lorenzo.bianconi@redhat.com \
--cc=davem@davemloft.net \
--cc=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).