From: Jakub Kicinski <kuba@kernel.org>
To: Tom Herbert <tom@herbertland.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
justin.iurman@uliege.be, willemdebruijn.kernel@gmail.com,
pabeni@redhat.com
Subject: Re: [PATCH net-next v9 00/10] ipv6: Address ext hdr DoS vulnerabilities
Date: Sat, 14 Mar 2026 10:58:17 -0700 [thread overview]
Message-ID: <20260314105817.6243c3cf@kernel.org> (raw)
In-Reply-To: <20260314175124.47010-1-tom@herbertland.com>
On Sat, 14 Mar 2026 10:51:14 -0700 Tom Herbert wrote:
> Subject: [PATCH net-next v9 00/10] ipv6: Address ext hdr DoS vulnerabilities
Sir, 24h between reposts, please. I could have told you that net-next
is our default tree, anyway. So you're just spamming the list and the
CI for no good reason.
Quoting documentation:
tl;dr
-----
- designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
- for fixes the ``Fixes:`` tag is required, regardless of the tree
- don't post large series (> 15 patches), break them up
- don't repost your patches within one 24h period
- reverse xmas tree
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#tl-dr
prev parent reply other threads:[~2026-03-14 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 17:51 [PATCH net-next v9 00/10] ipv6: Address ext hdr DoS vulnerabilities Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 01/10] ipv6: Check of max HBH or DestOp sysctl is zero and drop if it is Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 02/10] ipv6: Cleanup IPv6 TLV definitions Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 03/10] ipv6: Add case for IPV6_TLV_TNL_ENCAP_LIMIT in EH TLV switch Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 04/10] ipv6: Set HBH and DestOpt limits to 2 Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 05/10] ipv6: Document defaults for max_{dst|hbh}_opts_number sysctls Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 06/10] ipv6: Enforce Extension Header ordering Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 07/10] ipv6: Document enforce_ext_hdr_order sysctl Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 08/10] test: Add proto_nums.py in networking selftests Tom Herbert
2026-03-17 15:22 ` Simon Horman
2026-03-14 17:51 ` [PATCH net-next v9 09/10] test: Add ext_hdr.py " Tom Herbert
2026-03-17 15:24 ` [net-next,v9,09/10] " Simon Horman
2026-04-20 18:25 ` Tom Herbert
2026-03-14 17:51 ` [PATCH net-next v9 10/10] test: Add networking selftest for eh limits Tom Herbert
2026-03-17 15:32 ` Simon Horman
2026-04-20 18:23 ` Tom Herbert
2026-03-14 17:58 ` Jakub Kicinski [this message]
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=20260314105817.6243c3cf@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=justin.iurman@uliege.be \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tom@herbertland.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 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.