From: Thorsten Leemhuis <linux@leemhuis.info>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
helpdesk@kernel.org,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Please create the email alias do-not-apply-to-stable@kernel.org -> /dev/null
Date: Tue, 23 Apr 2024 09:28:42 +0200 [thread overview]
Message-ID: <99fe129c-d836-4a81-92df-f87a281ed799@leemhuis.info> (raw)
In-Reply-To: <20240422231550.3cf5f723@sal.lan>
On 23.04.24 00:15, Mauro Carvalho Chehab wrote:
>> stable@kernel.org is there to route to /dev/null on purpose so that
>> developers/maintainers who only want their patches to get picked up when
>> they hit Linus's tree, will have happen and not notify anyone else.
>> This is especially good when dealing with security-related things as we
>> have had MANY people accidentally leak patches way too early by having
>> cc: stable@vger.kernel.org in their signed-off-by areas, and forgetting
>> to tell git send-email to suppress cc: when sending them out for
>> internal review.
> Nice! didn't know about that. On a quick check, the only place at
> documentation mentioning it without vger is at checkpatch.rst.
>
> Perhaps it would make sense to document that as well.
Maybe something like the below?
Will add that to my next patch set unless I hear complaints.
Ciao, Thorsten
---
diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
index 727ad7f758e3e0..5a47ed06081e41 100644
--- a/Documentation/process/stable-kernel-rules.rst
+++ b/Documentation/process/stable-kernel-rules.rst
@@ -72,6 +72,10 @@ for stable trees, add this tag in the sign-off area::
Cc: stable@vger.kernel.org
+Use ``Cc: stable@kernel.org`` instead when fixing an unpublished vulnerability:
+it reduces the chance of someone exposing the fix to the public by way of
+'git send-email', as mails sent to that address are not delivered anywhere.
+
Once the patch is mainlined it will be applied to the stable tree without
anything else needing to be done by the author or subsystem maintainer.
prev parent reply other threads:[~2024-04-23 7:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 7:48 Please create the email alias do-not-apply-to-stable@kernel.org -> /dev/null Thorsten Leemhuis
2024-04-17 7:55 ` Greg KH
2024-04-17 8:09 ` Mauro Carvalho Chehab
2024-04-17 8:16 ` Greg KH
2024-04-17 8:48 ` Willy Tarreau
2024-04-17 17:13 ` Florian Fainelli
2024-04-17 16:56 ` Mauro Carvalho Chehab
2024-04-17 12:52 ` Konstantin Ryabitsev
2024-04-17 13:15 ` Vlastimil Babka
2024-04-17 13:21 ` Thorsten Leemhuis
2024-04-17 13:25 ` Konstantin Ryabitsev
2024-04-17 13:38 ` Greg KH
2024-04-17 13:55 ` Konstantin Ryabitsev
2024-04-18 7:04 ` Thorsten Leemhuis
2024-04-18 13:20 ` Greg KH
2024-04-22 15:49 ` Thorsten Leemhuis
2024-04-22 19:25 ` Konstantin Ryabitsev
2024-04-22 21:46 ` Mauro Carvalho Chehab
2024-04-22 22:04 ` Greg KH
2024-04-22 22:15 ` Mauro Carvalho Chehab
2024-04-23 7:28 ` Thorsten Leemhuis [this message]
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=99fe129c-d836-4a81-92df-f87a281ed799@leemhuis.info \
--to=linux@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=helpdesk@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sashal@kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).