All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: greg@kroah.com, 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 1/3] Documentation: security-bugs: do not systematically Cc the security team
Date: Tue, 5 May 2026 17:10:28 +0300	[thread overview]
Message-ID: <20260505141028.GF11063@unreal> (raw)
In-Reply-To: <20260503113506.5710-2-w@1wt.eu>

On Sun, May 03, 2026 at 01:35:04PM +0200, Willy Tarreau wrote:
> With the increase of automated reports, the security team is dealing
> with way more messages than really needed. The reporting process works
> well with most teams so there is no need to systematically involve the
> security team in reports.
> 
> Let's suggest to keep it for small lists of recipients and new reporters
> only. This should continue to cover the risk of lost messages while
> reducing the volume from prolific reporters.
> 
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Cc: Leon Romanovsky <leon@kernel.org>
> Signed-off-by: Willy Tarreau <w@1wt.eu>
> ---
>  Documentation/process/security-bugs.rst | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)

Thanks,
Reviewed-by: Leon Romanovsky <leon@kernel.org>

  reply	other threads:[~2026-05-05 14:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 11:35 [PATCH v2 0/3] Documentation: security-bugs: new updates covering triage and AI Willy Tarreau
2026-05-03 11:35 ` [PATCH v2 1/3] Documentation: security-bugs: do not systematically Cc the security team Willy Tarreau
2026-05-05 14:10   ` Leon Romanovsky [this message]
2026-05-08 15:31   ` Greg KH
2026-05-03 11:35 ` [PATCH v2 2/3] Documentation: security-bugs: explain what is and is not a security bug Willy Tarreau
2026-05-05 14:10   ` 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
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
2026-05-03 11:35 ` [PATCH v2 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports Willy Tarreau
2026-05-05 14:09   ` Leon Romanovsky

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=20260505141028.GF11063@unreal \
    --to=leon@kernel.org \
    --cc=corbet@lwn.net \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=w@1wt.eu \
    --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.