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:   Wed, 24 Aug 2022 19:58:19 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Steve French <smfrench@...il.com>
Cc:     Stable <stable@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: "Fixes:" vs. "Cc: stable ..."

On Wed, Aug 24, 2022 at 12:14:12PM -0500, Steve French wrote:
> Do changesets that already included the "Fixes:" tag in the commit
> description also need to include the "Cc: stable@...r.kernel.org" in
> order to be included in stable?

As per the documentation:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

You should be putting cc: stable@... on the patch.

But as not all maintainers do, we have to dig through those with Fixes:
in order to actually catch all bugfixes :(

So please, use cc: stable.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ