linux-kernel - Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2024041156-backache-dolly-a420@gregkh>
Date: Thu, 11 Apr 2024 07:29:40 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: Sasha Levin <sashal@...nel.org>, Jonathan Corbet <corbet@....net>,
	stable@...r.kernel.org, workflows@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no
 semi-automatic backport"

On Thu, Apr 11, 2024 at 07:25:04AM +0200, Thorsten Leemhuis wrote:
> Some developers deliberately steer clear of 'Fixes:' tags to prevent
> changes from being backported semi-automatically by the stable team.
> That somewhat undermines the reason for the existence of the Fixes: tag,
> hence point out there is an alternative to reach the same effect.
> 
> Link: https://lore.kernel.org/all/dfd87673-c581-4b4b-b37a-1cf5c817240d@leemhuis.info/
> Signed-off-by: Thorsten Leemhuis <linux@...mhuis.info>
> ---
>  Documentation/process/stable-kernel-rules.rst | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index 7bb16d42a51833..ebd57cb9277f7b 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -117,6 +117,12 @@ comment to pass arbitrary or predefined notes:
>     Note, such tagging is unnecessary if the stable team can derive the
>     appropriate versions from Fixes: tags.
>  
> + * Prevent semi-automatic backporting of changes carrying a 'Fixes:' tag:
> +
> +   .. code-block:: none
> +
> +     Cc: <stable@...r.kernel.org> # no semi-automatic backport

I do not understand, why are you saying "cc: stable" here if you do NOT
want it backported?

And what do you mean by "semi-automatic"?

confused,

greg k-h