The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	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 v2 2/3] Documentation: security-bugs: explain what is and is not a security bug
Date: Thu, 7 May 2026 17:48:27 +0200	[thread overview]
Message-ID: <afy0S-C87xn9DWUn@1wt.eu> (raw)
In-Reply-To: <CAHk-=whE=rLLbBRsFuQKVX49NgN2UUdUE=Druf3fiSZ9Ou8c3Q@mail.gmail.com>

On Thu, May 07, 2026 at 08:37:29AM -0700, Linus Torvalds wrote:
> On Thu, 7 May 2026 at 00:07, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > Perhaps also note that including a reproducer for a crash in public is
> > fine, including a full blown exploit is not.
> >
> > So perhaps that can serve as a guide
> 
> That would be a good rule, I think - and I like how it has the
> advantage of being very explicit and black-and-white, rather than some
> "I think my bug is so important that it should be sent to the speshul
> super-sikret list".
> 
> Because we all think we are special. Our mothers told us so, and even
> the AI bots are typically explicitly told to act as experts. So they
> think they are special too.

These points correspond to what I mentioned in my second message a few
hours ago, but I want to protect maintainers against the flood of crap
they're not necessarily used to. I think that the balance I proposed
could work as it more or less covers this. When you have a time to look
at it I'd be glad to have your opinion/criticism (sorry if it's a bit
long but the topic is far from being trivial).

willy

  reply	other threads:[~2026-05-07 15:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260503113506.5710-1-w@1wt.eu>
     [not found] ` <20260503113506.5710-4-w@1wt.eu>
2026-05-05 14:09   ` [PATCH v2 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports Leon Romanovsky
     [not found] ` <20260503113506.5710-2-w@1wt.eu>
2026-05-05 14:10   ` [PATCH v2 1/3] Documentation: security-bugs: do not systematically Cc the security team Leon Romanovsky
2026-05-08 15:31   ` Greg KH
     [not found] ` <20260503113506.5710-3-w@1wt.eu>
2026-05-05 14:10   ` [PATCH v2 2/3] Documentation: security-bugs: explain what is and is not a security bug Leon Romanovsky
2026-05-06 15:46   ` Linus Torvalds
2026-05-06 16:02     ` Willy Tarreau
2026-05-07  4:18       ` Willy Tarreau
2026-05-07  7:14         ` Peter Zijlstra
2026-05-07  7:07       ` Peter Zijlstra
2026-05-07 15:37         ` Linus Torvalds
2026-05-07 15:48           ` Willy Tarreau [this message]
2026-05-08 15:35     ` Greg KH
2026-05-08 15:54       ` Joshua Peisach
2026-05-08 16:07         ` Willy Tarreau
2026-05-08 15:59       ` Willy Tarreau
2026-05-08 16:39         ` Willy Tarreau
2026-05-09  6:39           ` Greg KH
2026-05-09  7:43             ` Willy Tarreau
2026-05-08 20:52   ` Shuah Khan
2026-05-09  4:48     ` Willy Tarreau
2026-05-09 19:50       ` Shuah Khan

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=afy0S-C87xn9DWUn@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=peterz@infradead.org \
    --cc=security@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=torvalds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox