linux-kernel - Re: [PATCH v2 5/5] docs: stable-kernel-rules: create special tag to flag 'no backporting'

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: <2024042914-bleep-imbecile-5f68@gregkh>
Date: Mon, 29 Apr 2024 09:51: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 v2 5/5] docs: stable-kernel-rules: create special tag to
 flag 'no backporting'

On Mon, Apr 29, 2024 at 09:18:30AM +0200, Thorsten Leemhuis wrote:
> Document a new variant of the stable tag developers can use to make the
> stable team's tools ignore a change[1].
> 
> That way developers can use 'Fixes:' tags without fearing the changes
> might be backported in semi-automatic fashion. Such concerns are the
> reason why some developers deliberately omit the 'Fixes:' tag in
> changes[2] -- which somewhat undermines the reason for the existence of
> that tag and might be unwise in the long term[3].
> 
> Link: https://lore.kernel.org/all/b452fd54-fdc6-47e4-8c26-6627f6b7eff3@leemhuis.info/ [1]
> Link: https://lore.kernel.org/all/cover.1712226175.git.antony.antony@secunet.com/ [2]
> Link: https://lore.kernel.org/all/dfd87673-c581-4b4b-b37a-1cf5c817240d@leemhuis.info/ [3]
> Signed-off-by: Thorsten Leemhuis <linux@...mhuis.info>
> 
> ---
> 
> A patch to make one of the stable-script honor the flag can be found in
> https://lore.kernel.org/all/655ce2a3-eb04-4ade-999e-23fc5dc5fb3a@leemhuis.info/
> 
> For autosel I was unable to locate the code.
> ---
>  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 ebf4152659f2d0..9ca8083b41c7f1 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -129,6 +129,12 @@ comment to pass arbitrary or predefined notes:
>  
>      Cc: <stable@...r.kernel.org> # see patch description, needs adjustments for <= 6.3
>  
> +There furthermore is a variant of the stable tag you can use to make the stable
> +team's backporting tools (e.g AUTOSEL or scripts that look for commits
> +containing a 'Fixes:' tag) ignore a change::
> +
> +     Cc: <stable+noautosel@...nel.org> # reason goes here, and must be present
> +
>  .. _option_2:
>  

Thanks for seeing this through:

Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>