linux/security/integrity
Frederick Lawler 30d68cb0c3 ima: process_measurement() needlessly takes inode_lock() on MAY_READ
On IMA policy update, if a measure rule exists in the policy,
IMA_MEASURE is set for ima_policy_flags which makes the violation_check
variable always true. Coupled with a no-action on MAY_READ for a
FILE_CHECK call, we're always taking the inode_lock().

This becomes a performance problem for extremely heavy read-only workloads.
Therefore, prevent this only in the case there's no action to be taken.

Signed-off-by: Frederick Lawler <fred@cloudflare.com>
Acked-by: Roberto Sassu <roberto.sassu@huawei.com>
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
2025-04-22 16:39:32 +02:00
..
evm integrity: fix typos and spelling errors 2025-02-04 21:36:43 -05:00
ima ima: process_measurement() needlessly takes inode_lock() on MAY_READ 2025-04-22 16:39:32 +02:00
platform_certs
Kconfig
Makefile
digsig.c
digsig_asymmetric.c crypto: sm2 - Remove sm2 algorithm 2024-06-07 19:46:39 +08:00
iint.c
integrity.h integrity: Use static_assert() to check struct sizes 2024-10-09 22:49:40 -04:00
integrity_audit.c