Re: [PATCH v2 069/110] 9p: replace PRIino with %llu/%llx format strings
Christian Schoenebeck <[email protected]> Tue, 03 Mar 2026 13:12:51 +0100
| Newsgroups | org.kernel.vger.autofs,dev.linux.lists.fsverity,dev.linux.lists.netfs,dev.linux.lists.ntfs3,dev.linux.lists.nvdimm,dev.linux.lists.ocfs2-devel,dev.linux.lists.v9fs,net.sourceforge.lists.linux-f2fs-devel,org.freedesktop.lists.amd-gfx,org.freedesktop.lists.dri-devel,org.infradead.lists.linux-mtd,org.kernel.vger.audit,org.kernel.vger.bpf,org.kernel.vger.ceph-devel,org.kernel.vger.ecryptfs,org.kernel.vger.linux-bluetooth,org.kernel.vger.linux-can,org.kernel.vger.linux-cifs,org.kernel.vger.linux-ext4,org.kernel.vger.linux-fscrypt,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-hams,org.kernel.vger.linux-integrity,org.kernel.vger.linux-kernel,org.kernel.vger.linux-media,org.kernel.vger.linux-nfs,org.kernel.vger.linux-nilfs,org.kernel.vger.linux-perf-users,org.kernel.vger.linux-sctp,org.kernel.vger.linux-security-module,org.kernel.vger.linux-trace-kernel,org.kernel.vger.linux-unionfs,org.kernel.vger.linux-x25,org.kernel.vger.linux-xfs,org.kernel.vger.netdev,org.kernel.vger.selinux,org.kvack.linux-mm |
|---|---|
| Message-ID | <13960165.uLZWGnKmhe@weasel> |
On Monday, 2 March 2026 21:24:53 CET Jeff Layton wrote: > Now that i_ino is u64 and the PRIino format macro has been removed, > replace all uses in 9p with the concrete format strings. > > Signed-off-by: Jeff Layton <[email protected]> > --- > fs/9p/vfs_addr.c | 4 ++-- > fs/9p/vfs_inode.c | 6 +++--- > fs/9p/vfs_inode_dotl.c | 6 +++--- > 3 files changed, 8 insertions(+), 8 deletions(-) 9p uses the following macro to convert the 9p network protocol's QID path from u64 (all platforms) to ino_t. The 32-bit path of this macro should be dropped after this change, as it would unnecessarily truncate the value to 32-bit now [fs/9p/v9fs_vfs.h]: #if (BITS_PER_LONG == 32) #define QID2INO(q) ((ino_t) (((q)->path+2) ^ (((q)->path) >> 32))) #else #define QID2INO(q) ((ino_t) ((q)->path+2)) #endif You are not breaking anything, if you happen to send a v3, that would be nice to be dropped, otherwise we'll handle that on our end later on: Reviewed-by: Christian Schoenebeck <[email protected]> I wonder whether that exceeded Claude's context size, or if that's in line with the prompt specified by you. /Christian