Thread (101 messages) 101 messages, 21 authors, 2026-02-27

Re: [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64

From: Matthew Wilcox <willy@infradead.org>
Date: 2026-02-26 16:50:36
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-mm, linux-nfs, linux-perf-users, linux-security-module, linux-unionfs, linux-xfs, lkml, netdev, netfs, ntfs3, nvdimm, ocfs2-devel, selinux, v9fs

On Thu, Feb 26, 2026 at 10:55:02AM -0500, Jeff Layton wrote:
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?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help