All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Herbert <tom@herbertland.com>
To: tom@herbertland.com, davem@davemloft.net, kuba@kernel.org,
	netdev@vger.kernel.org
Subject: [PATCH net-next 5/5] ipv6: Document default of one for max_hbh_opts_number
Date: Mon,  1 Dec 2025 10:55:34 -0800	[thread overview]
Message-ID: <20251201185817.1003392-6-tom@herbertland.com> (raw)
In-Reply-To: <20251201185817.1003392-1-tom@herbertland.com>

Changge documentation that the default limit for number of
Hop-by-Hop options is one
---
 Documentation/networking/ip-sysctl.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
index 7ccfdc74dc91..de078f7f6a17 100644
--- a/Documentation/networking/ip-sysctl.rst
+++ b/Documentation/networking/ip-sysctl.rst
@@ -2503,7 +2503,7 @@ max_hbh_opts_number - INTEGER
         and the number of known TLVs allowed is the absolute value of this
         number.
 
-        Default: 8
+        Default: 1
 
 max_dst_opts_length - INTEGER
 	Maximum length allowed for a Destination options extension
-- 
2.43.0


  parent reply	other threads:[~2025-12-01 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 18:55 [PATCH net-next 0/5] ipv6: Disable IPv6 Destination Options RX processing by default Tom Herbert
2025-12-01 18:55 ` [PATCH net-next 1/5] ipv6: Check if max HBH or DestOp sysctl is zero and drop if it is Tom Herbert
2025-12-01 18:55 ` [PATCH net-next 2/5] ipv6: Disable IPv6 Destination Options RX processing by default Tom Herbert
2025-12-01 18:55 ` [PATCH net-next 3/5] ipv6: Set Hop-by-Hop options limit to 1 Tom Herbert
2025-12-01 18:55 ` [PATCH net-next 4/5] ipv6: Document default of zero for max_dst_opts_number Tom Herbert
2025-12-01 18:55 ` Tom Herbert [this message]
2025-12-05  0:08 ` [PATCH net-next 0/5] ipv6: Disable IPv6 Destination Options RX processing by default Jakub Kicinski
2025-12-05 16:07   ` 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=20251201185817.1003392-6-tom@herbertland.com \
    --to=tom@herbertland.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --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 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.