From: Tom Herbert <tom@herbertland.com>
To: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
justin.iurman@uliege.be, willemdebruijn.kernel@gmail.com,
pabeni@redhat.com
Cc: Tom Herbert <tom@herbertland.com>
Subject: [PATCH net-next v7 07/10] ipv6: Document enforce_ext_hdr_order sysctl
Date: Wed, 4 Feb 2026 14:51:51 -0800 [thread overview]
Message-ID: <20260204225154.58245-8-tom@herbertland.com> (raw)
In-Reply-To: <20260204225154.58245-1-tom@herbertland.com>
Document the enforce_ext_hdr_order sysctl that controls whether
Extension Header order is enforced on receive.
Signed-off-by: Tom Herbert <tom@herbertland.com>
---
Documentation/networking/ip-sysctl.rst | 34 ++++++++++++++++++++++++--
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
index bafb2ab08d0e..ce783551b687 100644
--- a/Documentation/networking/ip-sysctl.rst
+++ b/Documentation/networking/ip-sysctl.rst
@@ -2487,8 +2487,8 @@ max_dst_opts_number - INTEGER
Default: 2
max_hbh_opts_number - INTEGER
- Maximum number of non-padding TLVs allowed in a Hop-by-Hop
- options extension header. If this value is zero then receive
+ Maximum number of non-padding TLVs allowed in a Hop-by-Hop
+ options extension header. If this value is zero then receive
Hop-by-Hop Options processing is disabled in which case packets
with the Hop-by-Hop Options extension header are dropped.
If this value is less than zero then unknown options are disallowed
@@ -2583,6 +2583,36 @@ ioam6_id_wide - LONG INTEGER
Default: 0xFFFFFFFFFFFFFF
+enforce_ext_hdr_order - BOOLEAN
+ Enforce recommended Extension Header ordering in RFC8200.
+ If the sysctl is set to 1 then the ordering is enforced in
+ received packets and each Extension Header may be present
+ at most once per packet (except for Destination Options that
+ may occur twice). If the sysctl is set to 0 then ordering is
+ not enforced and Extension Headers may be present in any
+ order and have any number of occurrences per packet (except
+ for Hop-by-Hop Options that must always be the first Extension
+ Header and occur at most once in a packet)).
+
+ The Extension Header order is:
+
+ IPv6 header
+ Hop-by-Hop Options header
+ Destination Options before the Routing header
+ Routing header
+ Fragment header
+ Authentication header
+ Encapsulating Security Payload header
+ Destination Options header
+ Upper-Layer header
+
+ Possible values:
+
+ - 0 (disabled)
+ - 1 (enabled)
+
+ Default: 1 (enabled)
+
IPv6 Fragmentation:
ip6frag_high_thresh - INTEGER
--
2.43.0
next prev parent reply other threads:[~2026-02-04 22:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 22:51 [PATCH net-next v7 00/10] ipv6: Address ext hdr DoS vulnerabilities Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 01/10] ipv6: Check of max HBH or DestOp sysctl is zero and drop if it is Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 02/10] ipv6: Cleanup IPv6 TLV definitions Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 03/10] ipv6: Add case for IPV6_TLV_TNL_ENCAP_LIMIT in EH TLV switch Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 04/10] ipv6: Set HBH and DestOpt limits to 2 Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 05/10] ipv6: Document defaults for max_{dst|hbh}_opts_number sysctls Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 06/10] ipv6: Enforce Extension Header ordering Tom Herbert
2026-02-04 22:51 ` Tom Herbert [this message]
2026-02-04 22:51 ` [PATCH net-next v7 08/10] test: Add proto_nums.py in networking selftests Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 09/10] test: Add ext_hdr.py " Tom Herbert
2026-02-06 2:45 ` [PATCH net-next v7 00/10] ipv6: Address ext hdr DoS vulnerabilities Jakub Kicinski
[not found] ` <CALx6S3576DLyd18BnFRkaNMhxb-Y3bsy8YJXy3-Q43EQVppEDQ@mail.gmail.com>
2026-02-11 19:16 ` Jakub Kicinski
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=20260204225154.58245-8-tom@herbertland.com \
--to=tom@herbertland.com \
--cc=davem@davemloft.net \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox