From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/3] icmp6: support rfc 4884
Date: Thu, 23 Jul 2020 10:33:54 -0400 [thread overview]
Message-ID: <20200723143357.451069-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
Extend the feature merged earlier this week for IPv4 to IPv6.
I expected this to be a single patch, but patch 1 seemed better to be
stand-alone
patch 1: small fix in length calculation
patch 2: factor out ipv4-specific
patch 3: add ipv6
Willem de Bruijn (3):
icmp: revise rfc4884 tests
icmp: prepare rfc 4884 for ipv6
icmp6: support rfc 4884
include/linux/icmp.h | 3 ++-
include/linux/ipv6.h | 1 +
include/uapi/linux/icmpv6.h | 1 +
include/uapi/linux/in6.h | 1 +
net/ipv4/icmp.c | 26 +++++++-------------------
net/ipv4/ip_sockglue.c | 14 +++++++++++++-
net/ipv6/datagram.c | 16 ++++++++++++++++
net/ipv6/ipv6_sockglue.c | 12 ++++++++++++
8 files changed, 53 insertions(+), 21 deletions(-)
--
2.28.0.rc0.105.gf9edc3c819-goog
next reply other threads:[~2020-07-23 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:33 Willem de Bruijn [this message]
2020-07-23 14:33 ` [PATCH net-next 1/3] icmp: revise rfc4884 tests Willem de Bruijn
2020-07-23 14:33 ` [PATCH net-next 2/3] icmp: prepare rfc 4884 for ipv6 Willem de Bruijn
2020-07-23 14:33 ` [PATCH net-next 3/3] icmp6: support rfc 4884 Willem de Bruijn
2020-07-23 16:44 ` Jakub Kicinski
2020-07-23 17:13 ` Willem de Bruijn
2020-07-24 2:25 ` kernel test robot
2020-07-24 2:25 ` kernel test robot
2020-07-24 4:33 ` kernel test robot
2020-07-24 4:33 ` kernel test robot
2020-07-24 4:33 ` [RFC PATCH] icmp6: ipv6_icmp_error_rfc4884() can be static kernel test robot
2020-07-24 4:33 ` kernel test robot
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=20200723143357.451069-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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.