Arjan van de Ven wrote: >> It seems like the posix idea of unique <st_dev, st_ino> doesn't >> hold water for modern file systems > > are you really sure? Well Jan's example was of Coda that uses 128-bit internal file ids. > and if so, why don't we fix *THAT* instead Hmm, sometimes you can't fix the world, especially if the filesystem is exported over NFS and has a problem with fitting its file IDs uniquely into a 64-bit identifier. > rather than adding racy > syscalls and such that just can't really be used right... > If the syscall is working on two pathnames I agree there might be a race that isn't different from calling lstat() on each of these names before opening them. But I'm not sure I see a race if you operate on two open file descriptors (compared to fstat()ing both of them) On the nfs side, if the client looked up two names (or opened them over nfsv4) and has two filehandles in hand, asking the server whether they refer to the same object isn't racy. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
