News for hackers. Stuff that matters.
Re:Tmpfs inode corruption: introducing inode64 by rav on Saturday September 04, 2021 @03:18AM (#28412849)
Since the contents are in-memory, you could imagine a straightforward implementation where the directory hierarchy in the tmpfs is stored in a pointer-based in-memory tree.

A file handle just needs a pointer to where in memory the contents are stored, and the inode numbers are computed on the side because it's part of the interface.

You don't want to use the pointers as inode numbers directly, since for security reasons the kernel doesn't want to export valid kernel pointers to user space.

Re:Tmpfs inode corruption: introducing inode64 by yencabulator on Wednesday September 08, 2021 @05:31PM (#28463318)
To play with these concepts, you can write a FUSE filesystem where each file has inode 42, while being wholly separate nodes & handles. Linux VFS doesn't really use the inode number internally for anything while a direntry is alive.