linux/security/integrity
Jeff Layton bef5b11087
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>
History 2026-03-17 15:38:49 +01:00
..
evm EVM: add comment describing why ino field is still unsigned long 2026-03-17 15:38:49 +01:00
ima Convert remaining multi-line kmalloc_obj/flex GFP_KERNEL uses 2026-02-22 08:26:33 -08:00
platform_certs integrity/platform_certs: Allow loading of keys in the static key management mode 2025-07-09 09:16:18 +05:30
digsig.c Convert 'alloc_obj' family to use the new default GFP_KERNEL argument 2026-02-21 17:09:51 -08:00
digsig_asymmetric.c pkcs7, x509: Rename ->digest to ->m 2026-01-30 11:33:08 +00:00
iint.c ima,evm: move initcalls to the LSM framework 2025-10-22 19:24:27 -04:00
integrity.h ima,evm: move initcalls to the LSM framework 2025-10-22 19:24:27 -04:00
integrity_audit.c treewide: change inode->i_ino from unsigned long to u64 2026-03-06 14:31:28 +01:00
Kconfig integrity: Select CRYPTO from INTEGRITY_ASYMMETRIC_KEYS 2025-10-03 07:50:56 -04:00
Makefile ima: Move to LSM infrastructure 2024-02-15 23:43:46 -05:00