| 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: Fri, 28 Jul 2006 19:55:34 -0400 From: Dave Jones <davej@...hat.com> To: Greg KH <greg@...ah.com> Cc: Nathan Scott <nathans@....com>, stable@...nel.org, Justin Piszcz <jpiszcz@...idpixels.com>, linux-kernel@...r.kernel.org Subject: Re: [stable] 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7? On Fri, Jul 28, 2006 at 04:26:54PM -0700, Greg Kroah-Hartman wrote: > > OK, 2.6.17.7 is out, but still - is this suggestion worthwhile > > considering for future -stable release engineering or just crap? > > .7 took a bit longer than expected, due to some security bugs that > needed to be added to the queue, combined with the fact that both Chris > and I were busy with OLS stuff. Normally we both aren't travelling at > the same time, but right then, we were, so we couldn't respond as > quickly as it seems some people felt we should have. > > Sorry about this, we'll try to do better next time. The flipside to this is that those patches had been posted for around a week before you released .7, and *no-one* caught this problem until after the release. The burden of testing shouldn't solely be on the -stable team. Perhaps a -pre release at the time of review would be a good idea. Just a roll-up of the proposed patches, to save testers having to save and apply 30 patches seperately ? Dave -- http://www.codemonkey.org.uk - 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