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
| ||
|
Date: Tue, 5 Apr 2022 23:24:13 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Guenter Roeck <linux@...ck-us.net> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org, stable@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com, f.fainelli@...il.com, sudipm.mukherjee@...il.com, slade@...dewatkins.com, Sasha Levin <sashal@...nel.org> Subject: Re: [PATCH 5.10 000/599] 5.10.110-rc1 review On Tue, 5 Apr 2022 23:08:12 -0400 Steven Rostedt <rostedt@...dmis.org> wrote: > Here's a thought, if you decide to backport a patch to stable, and you see > that there's another commit with a "Fixes" tag to the automatically > selected commit. DO NOT BACKPORT IF THE FIXES PATCH FAILS TO GO BACK TOO! Seriously. This should be the case for *all* backported patches, not just the AUTOSEL ones. Otherwise you are backporting a commit to "stable" that is KNOWN TO BE BROKEN! -- Steve
Powered by blists - more mailing lists