Re: [PATCH v2 049/110] security: use PRIino format for i_ino
From: Paul Moore <paul@paul-moore.com>
Date: 2026-03-03 02:28:29
Also in:
amd-gfx, autofs, bpf, ceph-devel, dri-devel, linux-bluetooth, linux-can, 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-sctp, linux-security-module, linux-trace-kernel, linux-unionfs, linux-xfs, lkml, netdev, netfs, nvdimm, ocfs2-devel, selinux, v9fs
On Mon, Mar 2, 2026 at 3:36 PM Jeff Layton [off-list ref] wrote:
Convert security i_ino format strings to use the PRIino format macro in preparation for the widening of i_ino via kino_t. Also correct signed format specifiers to unsigned, since inode numbers are unsigned values. Signed-off-by: Jeff Layton <jlayton@kernel.org> --- security/apparmor/apparmorfs.c | 4 ++-- security/integrity/integrity_audit.c | 2 +- security/ipe/audit.c | 2 +- security/lsm_audit.c | 10 +++++----- security/selinux/hooks.c | 10 +++++----- security/smack/smack_lsm.c | 12 ++++++------ 6 files changed, 20 insertions(+), 20 deletions(-)
No comment on the PRIino specifier, but the LSM framework and SELinux changes seem complete. Acked-by: Paul Moore <paul@paul-moore.com> (LSM/SELinux) -- paul-moore.com