[...]
> FAT-derived filesystems use directory entry location as inode
> number. Fine, except that we have to take care of unlinked-but-opened
> inodes (avoid reusing the same number). Thus we may have to declare a
> directory busy even if all files are unlinked (otherwise we might reuse
> the same block and thus inode numbers later) [not done; race in msdos and
> umsdos]. Thus we have to do all sorts of ugly stuff in link creation.
How about using the number of the first cluster in the file as the inode
number? As far as I understand, on FATish filesystems that is the way you
get at the real file data, so it can't change under you, whatever else is
going on. Or am I missing something here?
-- Horst von Brand vonbrand@sleipnir.valparaiso.cl Casilla 9G, Viņa del Mar, Chile +56 32 672616- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/