[ I/O socket time out. Trimming the To list.]
On Wed, 2026-03-04 at 10:32 -0500, Jeff Layton wrote:
This version squashes all of the format-string changes and the i_ino type change into the same patch. This results in a giant 600+ line patch at the end of the series, but it does remain bisectable. Because the patchset was reorganized (again) some of the R-b's and A-b's have been dropped.
The entire pile is in the "iino-u64" branch of my tree, if anyone is interested in testing this.
https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git/Original cover letter follows:
----------------------8<-----------------------
Christian said [1] to "just do it" when I proposed this, so here we are!
For historical reasons, the inode->i_ino field is an unsigned long, which means that it's 32 bits on 32 bit architectures. This has caused a number of filesystems to implement hacks to hash a 64-bit identifier into a 32-bit field, and deprives us of a universal identifier field for an inode.
This patchset changes the inode->i_ino field from an unsigned long to a u64. This shouldn't make any material difference on 64-bit hosts, but 32-bit hosts will see struct inode grow by at least 4 bytes. This could have effects on slabcache sizes and field alignment.
The bulk of the changes are to format strings and tracepoints, since the kernel itself doesn't care that much about the i_ino field. The first patch changes some vfs function arguments, so check that one out carefully.
With this change, we may be able to shrink some inode structures. For instance, struct nfs_inode has a fileid field that holds the 64-bit inode number. With this set of changes, that field could be eliminated. I'd rather leave that sort of cleanups for later just to keep this simple.
Much of this set was generated by LLM, but I attributed it to myself since I consider this to be in the "menial tasks" category of LLM usage.
Signed-off-by: Jeff Layton jlayton@kernel.org
Jeff, missing from this patch set is EVM. In hmac_add_misc() EVM copies the i_ino and calculates either an HMAC or file meta-data hash, which is then signed.
Mimi