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
Cc: Tom Herbert <tom@herbertland.com>,
Justin Iurman <justin.iurman@gmail.com>,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next v6 03/10] ipv6: Add case for IPV6_TLV_TNL_ENCAP_LIMIT in EH TLV switch
Date: Mon, 2 Feb 2026 16:48:46 -0800 [thread overview]
Message-ID: <20260203004853.94438-4-tom@herbertland.com> (raw)
In-Reply-To: <20260203004853.94438-1-tom@herbertland.com>
IPV6_TLV_TNL_ENCAP_LIMIT is a recognized Destination option that is
processed in ip_tunnel.c. Add a case for it in the switch in
ip6_parse_tlv so that it is recognized as a known option.
Also remove the unlikely around the check for max_count < 0 since the
default limits for HBH and Destination options can be less than zero.
Signed-off-by: Tom Herbert <tom@herbertland.com>
Reviewed-by: Justin Iurman <justin.iurman@gmail.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
---
net/ipv6/exthdrs.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/net/ipv6/exthdrs.c b/net/ipv6/exthdrs.c
index f7f7bcf9395a..85f1b65d4c98 100644
--- a/net/ipv6/exthdrs.c
+++ b/net/ipv6/exthdrs.c
@@ -122,7 +122,7 @@ static bool ip6_parse_tlv(bool hopbyhop,
int tlv_count = 0;
int padlen = 0;
- if (unlikely(max_count < 0)) {
+ if (max_count < 0) {
disallow_unknowns = true;
max_count = -max_count;
}
@@ -202,6 +202,16 @@ static bool ip6_parse_tlv(bool hopbyhop,
if (!ipv6_dest_hao(skb, off))
return false;
break;
+#endif
+#if IS_ENABLED(CONFIG_IPV6_TUNNEL)
+ case IPV6_TLV_TNL_ENCAP_LIMIT:
+ /* The tunnel encapsulation option.
+ * This is handled in ip6_tunnel.c so
+ * we don't need to do anything here
+ * except to accept it as a recognized
+ * option
+ */
+ break;
#endif
default:
if (!ip6_tlvopt_unknown(skb, off,
--
2.43.0
next prev parent reply other threads:[~2026-02-03 0:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 0:48 [PATCH net-next v6 00/10] ipv6: Address ext hdr DoS vulnerabilities Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 01/10] ipv6: Check of max HBH or DestOp sysctl is zero and drop if it is Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 02/10] ipv6: Cleanup IPv6 TLV definitions Tom Herbert
2026-02-03 0:48 ` Tom Herbert [this message]
2026-02-03 0:48 ` [PATCH net-next v6 04/10] ipv6: Set HBH and DestOpt limits to 2 Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 05/10] ipv6: Document defaults for max_{dst|hbh}_opts_number sysctls Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 06/10] ipv6: Enforce Extension Header ordering Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 07/10] ipv6: Document enforce_ext_hdr_order sysctl Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 08/10] test: Add proto_nums.py in networking selftests Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 09/10] test: Add ext_hdr.py " Tom Herbert
2026-02-03 0:48 ` [PATCH net-next v6 10/10] test: Add networking sefltest for eh limits Tom Herbert
2026-02-03 10:07 ` Paolo Abeni
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=20260203004853.94438-4-tom@herbertland.com \
--to=tom@herbertland.com \
--cc=davem@davemloft.net \
--cc=justin.iurman@gmail.com \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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