]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
EVM: add comment describing why ino field is still unsigned long
authorJeff Layton <jlayton@kernel.org>
Mon, 16 Mar 2026 19:02:22 +0000 (15:02 -0400)
committerChristian Brauner <brauner@kernel.org>
Tue, 17 Mar 2026 14:38:49 +0000 (15:38 +0100)
commitbef5b11087ce87df47f621c02c1027557d886caf
tree3a960dc00dc6233c7c891878d242ea10504d9002
parent9840bb66e7e5dffd72b03201318f154a10b06b4a
EVM: add comment describing why ino field is still unsigned long

Mimi pointed out that we didn't widen the inode number field in struct
h_misc alongside the inode->i_ino widening. While we could make an
equivalent change there, that would require EVM resigning on all 32-bit
hosts.

Instead, leave the field as an unsigned long. This should have no effect
on 64-bit hosts, and allow things to continue working on 32-bit hosts in
the cases where the i_ino fits in 32-bits.

Add a comment explaining why it's being left as unsigned long.

Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Link: https://patch.msgid.link/20260316-iino-u64-v3-1-d1076b8f7a20@kernel.org
Signed-off-by: Christian Brauner <brauner@kernel.org>
security/integrity/evm/evm_crypto.c