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: Sat, 14 Apr 2012 18:02:42 +0200 From: Willy Tarreau <w@....eu> To: Felipe Contreras <felipe.contreras@...il.com> Cc: Jonathan Nieder <jrnieder@...il.com>, Stefan Richter <stefanr@...6.in-berlin.de>, Adrian Chadd <adrian@...ebsd.org>, Greg KH <gregkh@...uxfoundation.org>, Sergio Correia <lists@...e.net>, linux-kernel@...r.kernel.org, stable@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, linux-wireless Mailing List <linux-wireless@...r.kernel.org>, Sujith Manoharan <c_manoha@....qualcomm.com>, "ath9k-devel@...ts.ath9k.org" <ath9k-devel@...ema.h4ckr.net>, "John W. Linville" <linville@...driver.com> Subject: Re: [ 00/78] 3.3.2-stable review On Sat, Apr 14, 2012 at 06:43:06PM +0300, Felipe Contreras wrote: > I understand you use 'stable' as guarantee, and I know it works, but > do you *need* this guarantee? > > And before you go on why you need this guarantee to avoid fixes to be > lost, this is an *entirely different thing*; we are not talking about > fixes in 'stable' that don't exist in mainline--for which there is > evidence that those caused problems in the past, we are talking about > reverting patches from 'stable' that are not part of the upstream > release from where the 'stable' branch was forked--*nobody* has showed > any evidence that this has happened before and caused issues. Why make a special case for the version from which stable was derived ? That doesn't make sense at all to me since by definition, *all* patches that are in stable were not in this version ! Take it simpler if you want : *all* patches in stable need an upstream commit ID, whether they're backports or reverts. You don't revert a patch from stable, you backport a revert from upstream. Willy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists