Re: [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64
From: Jeff Layton <jlayton@kernel.org>
Date: 2026-02-26 17:01:57
Also in:
amd-gfx, autofs, ceph-devel, linux-cifs, linux-ext4, linux-f2fs-devel, linux-fscrypt, linux-fsdevel, linux-hams, linux-integrity, linux-media, linux-nfs, linux-perf-users, linux-security-module, linux-trace-kernel, linux-unionfs, linux-xfs, lkml, netdev, netfs, ntfs3, nvdimm, ocfs2-devel, selinux, v9fs
On Thu, 2026-02-26 at 16:49 +0000, Matthew Wilcox wrote:
On Thu, Feb 26, 2026 at 10:55:02AM -0500, Jeff Layton wrote:quoted
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.Why are the format strings all done as separate patches? Don't we get bisection hazards by splitting it apart this way?
One big patch would be Yuuuuge. We could certainly do it that way, but it'll be nightmare if we ever do have to revert part of it. What do you suggest? -- Jeff Layton [off-list ref]