On Thu, 2022-10-13 at 15:36 -0700, Kees Cook wrote: > Move "integrity" LSM to the end of the Kconfig list and prepare for > having ima and evm LSM initialization called from the top-level > "integrity" LSM. The securityfs integrity directory and the "iint_cache" are shared IMA/EVM resources. Just because the "iint_cache" was on an LSM hook, it should never have been treated as an LSM on its own. IMA maintains and verifies file data integrity, while EVM maintains and verifies file metadata integrity. IMA and EVM may both be configured and enabled, or independently of each other. However, only if either IMA or EVM are configured and enabled, should the iint_cache be created. There is absolutely no need for an independent "integrity" LSM. -- thanks, Mimi
