Tmpfs inode corruption: introducing inode64

Ran into this: tmpfs inode corruption: introducing inode64

Seems like an interesting tidbit

In essence, the patches move tmpfs’ inode allocation away from the get_next_ino shared pool, in favour of our own superblock-based system, and add support for 64-bit inodes using the inode64 tmpfs mount option (or allow having it on by default by enabling CONFIG_TMPFS_INODE64 when compiling the kernel).

So, am I reading it right that issues would come up when a very large number of files would be created in a tmpfs partition? And this fixes that?

So this applies to systems that have, like, 1TB+ of RAM?

Or am I completely wrong here?