On 02/26/13 13:48, Nix wrote: > #2 0x00000000004021e0 in test_utimens (print=print@entry=true, func=0x401890 > <do_utimensat>) at test-utimens.h:35
If that line number is right, the test program did a creat (file, 0600) that succeeded, followed by a stat (file, &st) that failed. Offhand the only way I can see that happening, other than a bug in the underlying system or a weird resource failure or some other process mucking things up, is if you're running a 32-bit application and the file system assigned a big inode number to the file, so large that it won't fit in 32 bits. Is that possible? (If so, don't do that. :-)
