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, 3 Dec 2010 16:07:19 -0500 From: Paul Gortmaker <paul.gortmaker@...driver.com> To: Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, torvalds@...ux-foundation.org, stable@...nel.org, jason.wessel@...driver.com Cc: Andi Kleen <andi@...stfloor.org>, lwn@....net Subject: Announcement: Plans for v2.6.34-longterm Firstly, I'd like to thank Greg for all the past work he's done on juggling all these different stable releases - many people have reaped the benefits of them for quite some time, and it only makes sense to spread the loading around as it has grown significantly. With that in mind, it is our intention to also maintain a 2.6.34 longterm tree. Jason and I work at Wind River, which already has released products based on v2.6.34, and as such it only makes sense to have a public long-term tree that others who are also based on 2.6.34 can make use of. I've already done an end-to-end audit of the current 2.6.32 longterm stable release, and used the list of these already "approved for stable" patches on v2.6.32 to identify 260 upstream commits that are applicable, but not yet present in the last 2.6.34.7 stable release. A candidate tree for 2.6.34.8 with the above 260 commits applied to it is available now for review/testing at: git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-2.6.34.y.git Note that there are no additional "non-stable" commits applied to this tree. It is purely commits that are already in use in a stable release. The next step will be to audit the 35-stable for appropriate content. This tree is currently undergoing internal testing at WR on various x86[64], ARM, MIPS and PowerPC targets, but of course any additional testing and feedback is most welcome. If anyone is interested in the audit data, I can send folks details on that too. Just as with Andi's longterm tree, the final details of where these will be finally located on kernel.org and so forth remains to be worked out and will be announced at a later date as things are finalized. Paul. -- 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