From: Tom Herbert <tom@herbertland.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: Tom Herbert <tom@herbertland.com>
Subject: [PATCH v4 net-next 0/7] ipv6: Extension header infrastructure
Date: Fri, 23 Aug 2019 12:13:56 -0700 [thread overview]
Message-ID: <1566587643-16594-1-git-send-email-tom@herbertland.com> (raw)
This patchset improves the IPv6 extension header infrastructure
to make extension headers more usable and scalable.
- Reorganize extension header files to separate out common
API components
- Create common TLV handler that will can be used in other use
cases (e.g. segment routing TLVs, UDP options)
- Allow registration of TLV handlers
- Elaborate on the TLV tables to include more characteristics
- Add a netlink interface to set TLV parameters (such as
alignment requirements, authorization to send, etc.)
- Enhance validation of TLVs being sent. Validation is strict
(unless overridden by admin) following that sending clause
of the robustness principle
- Allow non-privileged users to set Hop-by-Hop and Destination
Options if authorized by the admin
v2:
- Fix build errors from missing include file.
v3:
- Fix kbuild issue for ipv6_opt_hdr declared inside parameter list
in ipeh.h
v4:
- Resubmit
Tom Herbert (7):
ipeh: Create exthdrs_options.c and ipeh.h
ipeh: Move generic EH functions to exthdrs_common.c
ipeh: Generic TLV parser
ip6tlvs: Registration of TLV handlers and parameters
ip6tlvs: Add TX parameters
ip6tlvs: Add netlink interface
ip6tlvs: Validation of TX Destination and Hop-by-Hop options
include/net/ipeh.h | 208 ++++++++
include/net/ipv6.h | 12 +-
include/uapi/linux/in6.h | 6 +
include/uapi/linux/ipeh.h | 53 ++
net/dccp/ipv6.c | 2 +-
net/ipv6/Kconfig | 4 +
net/ipv6/Makefile | 3 +-
net/ipv6/calipso.c | 6 +-
net/ipv6/datagram.c | 51 +-
net/ipv6/exthdrs.c | 505 ++-----------------
net/ipv6/exthdrs_common.c | 1158 ++++++++++++++++++++++++++++++++++++++++++++
net/ipv6/exthdrs_options.c | 342 +++++++++++++
net/ipv6/ipv6_sockglue.c | 39 +-
net/ipv6/raw.c | 2 +-
net/ipv6/tcp_ipv6.c | 2 +-
net/ipv6/udp.c | 2 +-
net/l2tp/l2tp_ip6.c | 2 +-
net/sctp/ipv6.c | 2 +-
18 files changed, 1881 insertions(+), 518 deletions(-)
create mode 100644 include/net/ipeh.h
create mode 100644 include/uapi/linux/ipeh.h
create mode 100644 net/ipv6/exthdrs_common.c
create mode 100644 net/ipv6/exthdrs_options.c
--
2.7.4
next reply other threads:[~2019-08-23 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 19:13 Tom Herbert [this message]
2019-08-23 19:13 ` [PATCH v4 net-next 1/7] ipeh: Create exthdrs_options.c and ipeh.h Tom Herbert
2019-08-23 19:13 ` [PATCH v4 net-next 2/7] ipeh: Move generic EH functions to exthdrs_common.c Tom Herbert
2019-08-23 19:13 ` [PATCH v4 net-next 3/7] ipeh: Generic TLV parser Tom Herbert
2019-08-23 19:14 ` [PATCH v4 net-next 4/7] ip6tlvs: Registration of TLV handlers and parameters Tom Herbert
2019-08-23 22:16 ` David Miller
2019-08-23 19:14 ` [PATCH v4 net-next 5/7] ip6tlvs: Add TX parameters Tom Herbert
2019-08-23 19:14 ` [PATCH v4 net-next 6/7] ip6tlvs: Add netlink interface Tom Herbert
2019-08-23 19:14 ` [PATCH v4 net-next 7/7] ip6tlvs: Validation of TX Destination and Hop-by-Hop options Tom Herbert
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=1566587643-16594-1-git-send-email-tom@herbertland.com \
--to=tom@herbertland.com \
--cc=davem@davemloft.net \
--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).