From: Greg KH <gregkh@linuxfoundation.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Jonathan Corbet <corbet@lwn.net>,
Security Officers <security@kernel.org>,
kees@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: insist on the plain-text requirement for security reports
Date: Mon, 1 Dec 2025 07:38:17 +0100 [thread overview]
Message-ID: <2025120112-sublet-parasitic-18da@gregkh> (raw)
In-Reply-To: <20251129141741.19046-1-w@1wt.eu>
On Sat, Nov 29, 2025 at 03:17:41PM +0100, Willy Tarreau wrote:
> As the trend of AI-generated reports is growing, the trend of unreadable
> reports in gimmicky formats is following, and we cannot request that
> developers rely on online viewers to be able to read a security report
> full for formatting tags. Let's just insist on the plain text requirement
> a bit more.
>
> Signed-off-by: Willy Tarreau <w@1wt.eu>
> ---
> Documentation/process/security-bugs.rst | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
Looks good to me! Given the number of non-plain-text emails with binary
attachments we still get there, it's obvious not many people seem to
read this file, but it can't hurt! :)
I'll queue this up if Jon doesn't, after -rc1 is out. If he wants to
take it, here's my:
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2025-12-01 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 14:17 [PATCH] Documentation: insist on the plain-text requirement for security reports Willy Tarreau
2025-12-01 6:38 ` Greg KH [this message]
2025-12-01 7:12 ` Willy Tarreau
2025-12-22 22:32 ` Jonathan Corbet
2025-12-01 20:47 ` Ingo Molnar
2025-12-03 7:16 ` Willy Tarreau
2025-12-03 14:40 ` Kees Cook
2025-12-03 14:58 ` Willy Tarreau
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=2025120112-sublet-parasitic-18da@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@kernel.org \
--cc=w@1wt.eu \
/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).