Bernd Schubert <[EMAIL PROTECTED]> writes: >> It is most likely some kind of user space problem. I would change >> it to int err = stat(dir, &buf); >> and then go through it with gdb and see what value err gets assigned. >> >> I cannot see any kernel problem. > > The err value will become -1 here.
That's because there are some values in the stat64 buffer delivered by the kernel which cannot be packed into the stat buffer that you pass to stat. Use stat64 or _FILE_OFFSET_BITS=64. > Trond Myklebust already suggested to look at the results of errno: > > On Tuesday 01 March 2005 00:43, Bernd Schubert wrote: >> On Monday 28 February 2005 23:26, you wrote: >> > Given that strace shows that both syscalls (stat64() and stat()) >> > succeed, The trace does not say anything about the user-level stat(). >> [EMAIL PROTECTED] tests>./test_stat32 /mnt/test/yp >> stat for /mnt/test/yp failed >> ernno: 75 (Value too large for defined data type) >> >> But why does stat64() on a 64-bit kernel tries to fill in larger data than >> on a 32-bit kernel and larger data also only for nfs-mount points? Hmm, I >> will tomorrow compare the tcp-packges sent by the server. > > So I still think thats a kernel bug. This has nothing to do with the kernel. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - 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/