From: Willy Tarreau <w@1wt.eu>
To: Leon Romanovsky <leon@kernel.org>
Cc: greg@kroah.com, Jonathan Corbet <corbet@lwn.net>,
skhan@linuxfoundation.org, security@kernel.org,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Documentation: security-bugs: new updates covering triage and AI
Date: Sat, 9 May 2026 12:56:50 +0200 [thread overview]
Message-ID: <af8S8rF5yz5ghOk1@1wt.eu> (raw)
In-Reply-To: <20260509105222.GA15586@unreal>
On Sat, May 09, 2026 at 01:52:22PM +0300, Leon Romanovsky wrote:
> On Sat, May 09, 2026 at 11:47:52AM +0200, Willy Tarreau wrote:
> > This series tries to translate recent discussions on the security list
> > on how to better handle reports. It details:
> > - when not to Cc: the security list
> > - what classes of bugs do not need to be handled privately
> > - minimum requirements for AI-assisted reports
> >
> > As usual, this is probably perfectible but can already help in the short
> > term as we can point it to reporters, so barring any strong disagreement,
> > better continue to proceed in small incremental improvements and observe
> > the effects.
> >
> > Thanks!
> > Willy
>
> <...>
>
> > - Leon, I kept your reviewed-by since changes are very minimal and
> > didn't change the initial spirit.
>
> Thanks. The intent is the same, and I'm not the right person to argue over
> the precise wording anyway.
That was also my understanding, but thanks for confirming!
willy
next prev parent reply other threads:[~2026-05-09 10:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 9:47 [PATCH v3 0/3] Documentation: security-bugs: new updates covering triage and AI Willy Tarreau
2026-05-09 9:47 ` [PATCH v3 1/3] Documentation: security-bugs: do not systematically Cc the security team Willy Tarreau
2026-05-09 9:47 ` [PATCH v3 2/3] Documentation: security-bugs: explain what is and is not a security bug Willy Tarreau
2026-05-09 19:51 ` Shuah Khan
2026-05-11 17:28 ` Greg KH
2026-05-11 18:03 ` Willy Tarreau
2026-05-11 18:39 ` Jonathan Corbet
2026-05-11 20:26 ` Willy Tarreau
2026-05-11 20:42 ` Jonathan Corbet
2026-05-12 5:46 ` Greg KH
2026-05-12 5:54 ` Willy Tarreau
2026-05-12 17:20 ` Jonathan Corbet
2026-05-13 10:29 ` Greg KH
2026-05-13 11:23 ` Willy Tarreau
2026-05-13 12:52 ` Jonathan Corbet
2026-05-13 13:00 ` Willy Tarreau
2026-05-13 21:04 ` Jonathan Corbet
2026-05-14 4:32 ` Willy Tarreau
2026-05-14 12:22 ` Jonathan Corbet
2026-05-14 13:13 ` Willy Tarreau
2026-05-09 9:47 ` [PATCH v3 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports Willy Tarreau
2026-05-12 17:21 ` Jonathan Corbet
2026-05-13 10:30 ` Greg KH
2026-05-13 11:24 ` Willy Tarreau
2026-05-13 12:53 ` Jonathan Corbet
2026-05-13 12:58 ` Willy Tarreau
2026-05-13 21:02 ` Jonathan Corbet
2026-05-14 4:34 ` Willy Tarreau
2026-05-14 7:23 ` Greg KH
2026-05-09 10:52 ` [PATCH v3 0/3] Documentation: security-bugs: new updates covering triage and AI Leon Romanovsky
2026-05-09 10:56 ` Willy Tarreau [this message]
2026-05-12 17:14 ` Jonathan Corbet
2026-05-12 19:13 ` 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=af8S8rF5yz5ghOk1@1wt.eu \
--to=w@1wt.eu \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@kernel.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.