linux-kernel - Re: Is Fixes line enough?

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]

Date:   Tue, 23 Oct 2018 10:38:56 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Larry Finger <Larry.Finger@...inger.net>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: Is Fixes line enough?

On Tue, Oct 23, 2018 at 09:05:20AM -0500, Larry Finger wrote:
> Greg,
> 
> A question has come up on the linux-wireless ML. If a patch has a "Fixes"
> line, is that sufficient to get it flagged as a patch in Stable, or is a
> "Cc: Stable" line also needed?

Someone actually asked this question at the Maintainer's Summit,
actually.  The answer was that the Fixes line is not sufficient for
Greg's scripts; you have to have the "Cc: stable" line as well.  Greg
tried using the Fixes line as a trigger, but there were too many cases
where this pulled in commits that weren't really suitable for the
Stable kernels.  Sasha's machine-learning lash up will use the Fixes
line as a signal, but if you want to explicitly request that the patch
should be cherry-picked into Stable, you should have the "Cc: stable"
line.

(Also mentioned that at the Maintainer's Summit was that we probably
do need to take a look at the Stable documentation and see how it
needs to be updated to reflect how things are currently behind
handled.  :-)

Cheers,

						- Ted