On Wednesday 02 March 2005 17:53, Trond Myklebust wrote: > on den 02.03.2005 Klokka 12:33 (+0100) skreiv Bernd Schubert: > > > I can see no good reason for truncating inode number values on > > > platforms that actually do support 64-bit inode numbers, but I can see > > > several > > > > Well, at least we would have a reason ;) > > A 32-bit emulation mode is clearly a "platform" which does NOT support > 64-bit inode numbers, however there is (currently) no way for the kernel > to detect that you are running that. Any extra truncation should > therefore ideally be done by the emulation layer rather than the kernel > itself. >
I already found the function in glibc and it looks as if it would be rather easy to do it there. I only hope the glibc maintainers will accept this kind of fixes (hope they won't say that nobody needs this). Cheers, Bernd PS: Also many thanks for fixing other bugs in the NFS client. Until 2.6.9 init somehow could not open /dev/console on a readonly mountpoint. With 2.6.11 this problem has disappeared, thanks a lot for fixing this and other problems. I never had the time to write a bugreport for that. -- Bernd Schubert Physikalisch Chemisches Institut / Theoretische Chemie Universität Heidelberg INF 229 69120 Heidelberg e-mail: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
