| 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
| ||
|
Message-ID: <20090331124716.GG13356@mit.edu> Date: Tue, 31 Mar 2009 08:47:16 -0400 From: Theodore Tso <tytso@....edu> To: Fabio Comolli <fabio.comolli@...il.com> Cc: Chuck Ebbert <cebbert@...hat.com>, "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Ext4 tree backports for 2.6.27.13 and 2.6.28.2 On Tue, Mar 31, 2009 at 02:40:22PM +0200, Fabio Comolli wrote: > OK. Now I have on my box the 2.6.27.19 kernel. Do you mean that I have > to apply 19->20, 20->21 and then this patch? There are ext4-related fixes in the 19->20 patches. There are no ext4 related patches in 20->21, so whether or not you do this is optional (from the perspective of applying this patch). > Then mount the fs as ext4dev? Yes, same as before. I will note that there were some enhancements and some lower-priority bug fixes that don't get backported to 2.6.27 series, since sometimes it is extremely difficult to backport things as far as 2.6.27. So if your goal is to use this in production, 2.6.29 will almost certainly be a better bet. The number of people who test the 2.6.27 backports of ext4 are also much smaller. We provide it as a service those who for whatever reason refuse to update to newer kernels, but it's hard for me to offer guarantees. Best regards, - Ted -- 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