From: Jakub Kicinski <kuba@kernel.org>
To: Tom Herbert <tom@herbertland.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, justin.iurman@uliege.be
Subject: Re: [PATCH net-next v3 2/7] ipv6: Add case for IPV6_TLV_TNL_ENCAP_LIMIT in EH TLV switch
Date: Tue, 20 Jan 2026 16:08:58 -0800 [thread overview]
Message-ID: <20260120160858.1b0a941c@kernel.org> (raw)
In-Reply-To: <20260119211212.55026-3-tom@herbertland.com>
On Mon, 19 Jan 2026 13:12:07 -0800 Tom Herbert wrote:
> +#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,
Transient build failure here:
net/ipv6/exthdrs.c:207:10: error: use of undeclared identifier 'IPV6_TLV_TNL_ENCAP_LIMIT'
207 | case IPV6_TLV_TNL_ENCAP_LIMIT:
| ^~~~~~~~~~~~~~~~~~~~~~~~
--
pw-bot: cr
next prev parent reply other threads:[~2026-01-21 0:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 21:12 [PATCH net-next v3 0/7] ipv6: Address ext hdr DoS vulnerabilities Tom Herbert
2026-01-19 21:12 ` [PATCH net-next v3 1/7] ipv6: Check of max HBH or DestOp sysctl is zero and drop if it is Tom Herbert
2026-01-19 21:12 ` [PATCH net-next v3 2/7] ipv6: Add case for IPV6_TLV_TNL_ENCAP_LIMIT in EH TLV switch Tom Herbert
2026-01-21 0:08 ` Jakub Kicinski [this message]
2026-01-19 21:12 ` [PATCH net-next v3 3/7] ipv6: Cleanup IPv6 TLV definitions Tom Herbert
2026-01-19 21:12 ` [PATCH net-next v3 4/7] ipv6: Set HBH and DestOpt limits to 2 Tom Herbert
2026-01-19 21:12 ` [PATCH net-next v3 5/7] ipv6: Document defaults for max_{dst|hbh}_opts_number sysctls Tom Herbert
2026-01-19 21:12 ` [PATCH net-next v3 6/7] ipv6: Enforce Extension Header ordering Tom Herbert
2026-01-19 21:12 ` [PATCH net-next v3 7/7] ipv6: Document enforce_ext_hdr_order sysctl 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=20260120160858.1b0a941c@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=justin.iurman@uliege.be \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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