linux-kernel - Re: [RFC][PATCH] ima: Add support for staging measurements for deletion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <207fd6d7-53c-57bb-36d8-13a0902052d1@linux.microsoft.com>
Date: Wed, 10 Dec 2025 11:12:58 -0800 (PST)
From: Gregory Lumen <gregorylumen@...ux.microsoft.com>
To: Roberto Sassu <roberto.sassu@...weicloud.com>
cc: corbet@....net, zohar@...ux.ibm.com, dmitry.kasatkin@...il.com, 
    eric.snowberg@...cle.com, paul@...l-moore.com, jmorris@...ei.org, 
    serge@...lyn.com, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, 
    linux-integrity@...r.kernel.org, linux-security-module@...r.kernel.org, 
    chenste@...ux.microsoft.com, nramas@...ux.microsoft.com, 
    Roberto Sassu <roberto.sassu@...wei.com>
Subject: Re: [RFC][PATCH] ima: Add support for staging measurements for
 deletion

Roberto,

The proposed approach appears to be workable. However, if our primary goal 
here is to enable UM to free kernel memory consumed by the IMA log with an 
absolute minimum of kernel functionality/change, then I would argue that 
the proposed Stage-then-delete approach still represents unnecessary 
complexity when compared to a trim-to-N solution. Specifically:

- Any functional benefit offered through the introduction of a staged 
measurement list could be equally achieved in UM with a trim-to-N solution 
coupled with the proposed ima_measure_users counter for access locking.

- There exists a potential UM measurement-loss race condition introduced 
by the staging functionality that would not exist with a trim-to-N 
approach. (Occurs if a kexec call occurs after a UM agent has staged 
measurements for deletion, but has not completed copying them to 
userspace). This could be avoided by persisting staged measurements across 
kexec calls at the cost of making the proposed change larger.

Thanks,
-Gregory Lumen