From: Willy Tarreau <w@1wt.eu>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: greg@kroah.com, leon@kernel.org, security@kernel.org,
Jonathan Corbet <corbet@lwn.net>,
skhan@linuxfoundation.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports
Date: Mon, 27 Apr 2026 04:22:29 +0200 [thread overview]
Message-ID: <ae7IZZUwV7j7_czA@1wt.eu> (raw)
In-Reply-To: <133e96b7-251d-4af2-8084-2adca3e547e4@infradead.org>
On Sun, Apr 26, 2026 at 12:36:28PM -0700, Randy Dunlap wrote:
>
>
> On 4/26/26 9:39 AM, Willy Tarreau wrote:
> > +Use common sense when evaluating the report. If the affected file has not been
> > +touched for more than one year and is maintained by a single individual, it is
> > +likely that usage has declined and exposed users are virtually non-existent
> > +(e.g., drivers for very old hardware, obsolte filesystems). In such cases,
>
> obsolete
(...)
Thank you Randy for your reviews! I'll apply the fixes and resend in a
few days if there are no more comments.
Willy
next prev parent reply other threads:[~2026-04-27 2:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 16:39 [PATCH 0/3] Documentation: security-bugs: new updates covering triage and AI Willy Tarreau
2026-04-26 16:39 ` [PATCH 1/3] Documentation: security-bugs: do not systematically Cc the security team Willy Tarreau
2026-04-27 13:49 ` Greg KH
2026-04-27 15:24 ` Willy Tarreau
2026-04-27 15:33 ` Greg KH
2026-04-27 16:09 ` Willy Tarreau
2026-04-26 16:39 ` [PATCH 2/3] Documentation: security-bugs: explain what is and is not a security bug Willy Tarreau
2026-04-26 19:33 ` Randy Dunlap
2026-04-27 13:48 ` Greg KH
2026-04-27 15:27 ` Willy Tarreau
2026-04-27 15:35 ` Greg KH
2026-04-27 16:14 ` Willy Tarreau
2026-04-28 21:13 ` Greg KH
2026-04-29 3:09 ` Willy Tarreau
2026-04-29 6:10 ` Greg KH
2026-05-01 13:57 ` Willy Tarreau
2026-05-02 5:20 ` Demi Marie Obenour
2026-05-02 5:35 ` Willy Tarreau
2026-05-02 5:51 ` Demi Marie Obenour
2026-05-02 6:07 ` Willy Tarreau
2026-05-02 6:27 ` Demi Marie Obenour
2026-04-26 16:39 ` [PATCH 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports Willy Tarreau
2026-04-26 19:36 ` Randy Dunlap
2026-04-27 2:22 ` Willy Tarreau [this message]
2026-04-27 13:50 ` Greg KH
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=ae7IZZUwV7j7_czA@1wt.eu \
--to=w@1wt.eu \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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.