From: Willy Tarreau <w@1wt.eu>
To: Jonathan Corbet <corbet@lwn.net>
Cc: 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>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Subject: [PATCH v2 08/14] docs: security-bugs: explain what to do when a report gets no response
Date: Sat, 14 Nov 2026 20:00:08 +0100 [thread overview]
Message-ID: <20261114190014.17826-9-w@1wt.eu> (raw)
In-Reply-To: <20261114190014.17826-1-w@1wt.eu>
Some reports get lost, especially those with attachments or HTML, and
reporters sometimes wait for weeks for a response that will never come.
Since reports are private, the reporter has no other way to know if the
report was delivered than asking. The doc only mentioned resending a
message with no response within a week, in the middle of the rules
about copying the security team.
Let's explain it in "After sending the report": wait for a week, since
some maintainers are overloaded or only work in their spare time, then
resend the report with the security team in Cc. Also suggest to drop
any attachment and double-check the output format.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Willy Tarreau <w@1wt.eu>
---
Documentation/process/security-bugs.rst | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/Documentation/process/security-bugs.rst b/Documentation/process/security-bugs.rst
index 437f3cb29e80a..82ece82ecfb75 100644
--- a/Documentation/process/security-bugs.rst
+++ b/Documentation/process/security-bugs.rst
@@ -275,9 +275,7 @@ security team in any of the following cases:
this impact, and you will need to share any information you have;
* you are seeking specific help, such as when resending a message which got
- no response within a week (and please do not ask for feedback before such
- a delay, some subsystems have a long report queue, and some maintainers can
- only read them in their spare time).
+ no response within a week (see "After sending the report").
Otherwise, when a report of clear impact is sent to a larger team of clearly
identified maintainers, it is not necessary to Cc: the security list. Never
@@ -384,6 +382,19 @@ run additional tests. Reports where the reporter does not respond promptly
or cannot effectively discuss their findings may be abandoned if the
communication does not quickly improve.
+Messages sometimes get lost, especially those containing attachments or HTML.
+Since the report is private, you have no other way to know whether it was
+delivered than to ask. However, some subsystems have a long report queue, some
+maintainers are overloaded or only work in their spare time, so please wait for
+a week without any response before resending your report with the security team
+in Cc: (see above). In this case, be clear about the fact that it is a resend,
+and if possible, provide a reference to the original message. Better double
+check that the message is sent in plain text, and drop any attachment when
+resending, to increase the chances of successful delivery. In any case, please
+do not ask for proper receipt before this delay. This will not make your report
+be processed faster, will add extra load on maintainers and all you risk is
+your future messages being ignored.
+
Disclosure and embargoed information
------------------------------------
--
2.52.0
next prev parent reply other threads:[~2026-11-14 19:01 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 ` Willy Tarreau [this message]
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
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=20261114190014.17826-9-w@1wt.eu \
--to=w@1wt.eu \
--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=kuba@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=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 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.