| 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: Thu, 5 May 2011 16:58:55 +0200 From: Stanislaw Gruszka <sgruszka@...hat.com> To: Greg KH <greg@...ah.com> Cc: stable@...nel.org, linux-kernel@...r.kernel.org Subject: -longterm kernels (Was: Re: [stable] Patch Upstream: iwlwifi: fix skb usage after free) (Removing Cc as probably not interested, adding LKML) On Wed, May 04, 2011 at 03:36:05PM -0700, Greg KH wrote: > > Cc: stable@...nel.org # 2.6.32+ > > This doesn't apply to the .32 or .33-stable kernels. If you wish to see > it there, can someone please provide a backport and send it to > stable@...nel.org ? Done. BTW, Greg, perhaps -logterm releasing policy should be revised somehow. Currently we have .32, .33, .34, .35 -longterm, what is kind a much. If I could suggest something, would be nice to have longterm chosen versions predictable and constants i.e. one from every 3 kernel releases, like .35, .38, .41 ... . That would make distributions, that try to do release every half year very happy, because they will know what kernel to choose, which will be widely supported and tested. Also developers will have a bit less work with backporting fixes, as having same bug in n and n-3 release is less probable, than having the same bug in n and n-1. Stanislaw -- 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