From: Jakub Kicinski <kuba@kernel.org>
To: Tom Herbert <tom@herbertland.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] ipv6: Disable IPv6 Destination Options RX processing by default
Date: Thu, 4 Dec 2025 16:08:41 -0800 [thread overview]
Message-ID: <20251204160841.70fafdba@kernel.org> (raw)
In-Reply-To: <20251201185817.1003392-1-tom@herbertland.com>
On Mon, 1 Dec 2025 10:55:29 -0800 Tom Herbert wrote:
> Tom Herbert (5):
> ipv6: Check of max HBH or DestOp sysctl is zero and drop if it is
> ipv6: Disable IPv6 Destination Options RX processing by default
> ipv6: Set Hop-by-Hop options limit to 1
> ipv6: Document default of zero for max_dst_opts_number
> ipv6: Document default of one for max_hbh_opts_number
Hi Tom, the patches got marked as Changes Requested by someone,
not sure who. FWIW they are all missing our S-o-B.
net-next is now technically closed but I suppose you may want
to argue these are okay for net (if at all).
next prev parent reply other threads:[~2025-12-05 0:08 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 ` [PATCH net-next 5/5] ipv6: Document default of one for max_hbh_opts_number Tom Herbert
2025-12-05 0:08 ` Jakub Kicinski [this message]
2025-12-05 16:07 ` [PATCH net-next 0/5] ipv6: Disable IPv6 Destination Options RX processing by default 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=20251204160841.70fafdba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).