| 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: Tue, 3 Oct 2006 17:47:08 -0700 From: Chris Wedgwood <cw@...f.org> To: David Chinner <dgc@....com> Cc: xfs-dev@....com, xfs@....sgi.com, dhowells@...hat.com, LKML <linux-kernel@...r.kernel.org> Subject: Re: [RFC 0/3] Convert XFS inode hashes to radix trees On Wed, Oct 04, 2006 at 08:22:56AM +1000, David Chinner wrote: > That's a good question. In a recent thread on linux-fsdevel about > these patches Christoph Hellwig pointed out that 32bit user space is > not ready for 64 bit inodes, so it's probably going to be a while > before the second half of this mod is ready (which exports 64 bit > inodes ito userspace on 32bit platforms). yes a patch changing struct kstat and filldir* was merged... > http://marc.theaimsgroup.com/?l=linux-fsdevel&m=115946211808497&w=2 > http://marc.theaimsgroup.com/?l=linux-fsdevel&m=115948836023569&w=2 > As it stands, there's still a few barriers to getting 64 bit inodes > on 32 bit platforms and I can't see them going away quickly. Right > now I see little reason in moving to 64 bit inodes for 32 bit > platforms for XFS because of the 16TB filesystem size limit (that > only needs 33-36 bit inodes depending on the inode size) and no > 32bit platform is currently able to repair a filesystem of that > size. so that leaves NFS3+ is it really worth the pain then? - 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