| 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: <4DE9EE01.6070406@tao.ma> Date: Sat, 04 Jun 2011 16:34:09 +0800 From: Tao Ma <tm@....ma> To: Ted Ts'o <tytso@....edu> CC: ext4 development <linux-ext4@...r.kernel.org> Subject: Re: big allocation status On 06/04/2011 11:38 AM, Ted Ts'o wrote: > On Fri, Jun 03, 2011 at 09:57:23AM +0800, Tao Ma wrote: >> Hi Ted, >> >> Do you have any new branch or patch set that can be used for testing >> about big allocation? The latest patch set in the mailist is what you >> have sent at the beginning of May. Do you have an updated one? We will >> try to test it soon and it would grateful if we are on the same page. > > There is a patch set available at: > > git://repo.or.cz/ext4-patch-queue.git > > The bigalloc patches are after the stable-boundary, and will apply > against 3.0-rc1. Great thanks, we will schedule some test maybe next week. > > Note that I've fixed them up so that they apply on top of the punch > changes; however, the punch ioctl will not work correctly if bigalloc > is enabled, since that hasn't been fixed up yet. Fine, our test cases will not use punch ioctl AFAIK. > > Also, I'm still working on the e2fsprogs support. Cool, but do you have a mkfs.ext4 that we can let the kernel part work happily? Or we have to add the feature by hand by editing the disk format. ;) Regards, Tao -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists