From: Jakub Kicinski <kuba@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Jonathan Corbet <corbet@lwn.net>,
skhan@linuxfoundation.org, Randy Dunlap <rdunlap@infradead.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
gregkh@linuxfoundation.org, Johan Hovold <johan@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v2 14/14] docs: netdev: drop references to the securit list in the doc
Date: Sun, 15 Nov 2026 09:45:26 -0800 [thread overview]
Message-ID: <20261115094526.16015a28@kernel.org> (raw)
In-Reply-To: <20261114190014.17826-15-w@1wt.eu>
On Sat, 14 Nov 2026 20:00:14 +0100 Willy Tarreau wrote:
> The netdev maintainer profile asks reporters of bugs with possible
> security implications to use the public lists, which is consistent with
> the way most of these bugs are handled, but it says nothing about
> reproducers, and its suggested alternatives contradict security-bugs.rst:
> it points to the security team's address, and to the linux-distros list
> which must not be contacted before a fix is accepted. This text has been
> left unchanged since 2013 when security reports were not yet a problem,
> just because it remained unnoticed during the security doc refactoring.
>
> Instead of making a special case of security fixes, let's just drop
> this outdated section entirely, so that readers refer to the usual docs.
Acked-by: Jakub Kicinski <kuba@kernel.org>
Thanks!
prev parent reply other threads:[~2026-11-15 17:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 19:00 [PATCH v2 00/14] security-bugs doc updates Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 01/14] docs: security-bugs: reorganize the document without changing its contents Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 02/14] docs: security-bugs: clarify when to Cc the security team Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 03/14] docs: security-bugs: never publish reproducers of bugs with a security impact Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 04/14] docs: threat-model: clarify the case of automatically mounted file systems Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 05/14] docs: security-bugs: explain how to send a fix that can be applied Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 06/14] docs: security-bugs: do not send archives or binary attachments Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 07/14] docs: security-bugs: first-time reporters must send a single report first Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 08/14] docs: security-bugs: explain what to do when a report gets no response Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 09/14] docs: security-bugs: reports left unanswered for 7 days will be dropped Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 10/14] docs: security-bugs: add a section for maintainers receiving reports Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 11/14] docs: security-bugs: explain why directly sent reports add extra work Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 12/14] docs: security-bugs: explain why AI-found bugs are handled publicly Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 13/14] docs: submitting-patches: defer to security-bugs.rst for security fixes Willy Tarreau
2026-11-14 19:00 ` [PATCH v2 14/14] docs: netdev: drop references to the securit list in the doc Willy Tarreau
2026-11-15 17:45 ` 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=20261115094526.16015a28@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=johan@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=w@1wt.eu \
--cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox