linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: linux-integrity@vger.kernel.org
Cc: zohar@linux.ibm.com, serge@hallyn.com,
	christian.brauner@ubuntu.com, containers@lists.linux.dev,
	dmitry.kasatkin@gmail.com, ebiederm@xmission.com,
	krzysztof.struczynski@huawei.com, roberto.sassu@huawei.com,
	mpeters@redhat.com, lhinds@redhat.com, lsturman@redhat.com,
	puiterwi@redhat.com, jejb@linux.ibm.com, jamjoom@us.ibm.com,
	linux-kernel@vger.kernel.org, paul@paul-moore.com,
	rgb@redhat.com, linux-security-module@vger.kernel.org,
	jmorris@namei.org, jpenumak@redhat.com,
	Stefan Berger <stefanb@linux.ibm.com>
Subject: [PATCH v13 18/26] integrity: Add optional callback function to integrity_inode_free()
Date: Thu,  7 Jul 2022 10:47:52 -0400	[thread overview]
Message-ID: <20220707144800.828288-19-stefanb@linux.ibm.com> (raw)
In-Reply-To: <20220707144800.828288-1-stefanb@linux.ibm.com>

Add an optional callback function to integrity_inode_free() that,
if provided, must be called and determines whether the iint can be
freed. Adjust all callers of this function to provide a NULL pointer
since none of the existing callers needs this check.

Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
---
 include/linux/integrity.h |  8 ++++++--
 security/integrity/iint.c | 15 +++++++++++++--
 security/security.c       |  2 +-
 3 files changed, 20 insertions(+), 5 deletions(-)

diff --git a/include/linux/integrity.h b/include/linux/integrity.h
index 2ea0f2f65ab6..9fe826b9146e 100644
--- a/include/linux/integrity.h
+++ b/include/linux/integrity.h
@@ -19,10 +19,13 @@ enum integrity_status {
 	INTEGRITY_UNKNOWN,
 };
 
+struct integrity_iint_cache;
+typedef bool (*iint_removable_cb)(struct integrity_iint_cache *iint);
+
 /* List of EVM protected security xattrs */
 #ifdef CONFIG_INTEGRITY
 extern struct integrity_iint_cache *integrity_inode_get(struct inode *inode);
-extern void integrity_inode_free(struct inode *inode);
+extern void integrity_inode_free(struct inode *inode, iint_removable_cb check);
 extern void __init integrity_load_keys(void);
 
 #else
@@ -32,7 +35,8 @@ static inline struct integrity_iint_cache *
 	return NULL;
 }
 
-static inline void integrity_inode_free(struct inode *inode)
+static inline void integrity_inode_free(struct inode *inode,
+					iint_removable_cb check)
 {
 	return;
 }
diff --git a/security/integrity/iint.c b/security/integrity/iint.c
index 371cbceaf479..4580df0e716e 100644
--- a/security/integrity/iint.c
+++ b/security/integrity/iint.c
@@ -143,21 +143,32 @@ struct integrity_iint_cache *integrity_inode_get(struct inode *inode)
 /**
  * integrity_inode_free - called on security_inode_free
  * @inode: pointer to the inode
+ * @check: optional callback function to check whether the iint can be freed
  *
  * Free the integrity information(iint) associated with an inode.
  */
-void integrity_inode_free(struct inode *inode)
+void integrity_inode_free(struct inode *inode, iint_removable_cb check)
 {
 	struct integrity_iint_cache *iint;
+	bool freeit = true;
 
 	if (!IS_IMA(inode))
 		return;
 
 	write_lock(&integrity_iint_lock);
+
 	iint = __integrity_iint_find(inode);
-	rb_erase(&iint->rb_node, &integrity_iint_tree);
+
+	if (check)
+		freeit = check(iint);
+	if (freeit)
+		rb_erase(&iint->rb_node, &integrity_iint_tree);
+
 	write_unlock(&integrity_iint_lock);
 
+	if (!freeit)
+		return;
+
 	ima_free_ns_status_list(&iint->ns_list, &iint->ns_list_lock);
 
 	iint_free(iint);
diff --git a/security/security.c b/security/security.c
index 188b8f782220..7cf553b795da 100644
--- a/security/security.c
+++ b/security/security.c
@@ -1041,7 +1041,7 @@ static void inode_free_by_rcu(struct rcu_head *head)
 
 void security_inode_free(struct inode *inode)
 {
-	integrity_inode_free(inode);
+	integrity_inode_free(inode, NULL);
 	call_void_hook(inode_free_security, inode);
 	/*
 	 * The inode may still be referenced in a path walk and
-- 
2.36.1


  parent reply	other threads:[~2022-07-07 14:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 14:47 [PATCH v13 00/26] ima: Namespace IMA with audit support in IMA-ns Stefan Berger
2022-07-07 14:47 ` [PATCH v13 01/26] securityfs: rework dentry creation Stefan Berger
2022-07-07 14:47 ` [PATCH v13 02/26] securityfs: Extend securityfs with namespacing support Stefan Berger
2022-07-07 14:47 ` [PATCH v13 03/26] ima: Define ima_namespace struct and start moving variables into it Stefan Berger
2022-07-07 14:47 ` [PATCH v13 04/26] ima: Move arch_policy_entry into ima_namespace Stefan Berger
2022-07-07 14:47 ` [PATCH v13 05/26] ima: Move ima_htable " Stefan Berger
2022-07-07 14:47 ` [PATCH v13 06/26] ima: Move measurement list related variables " Stefan Berger
2022-07-07 14:47 ` [PATCH v13 07/26] ima: Move some IMA policy and filesystem " Stefan Berger
2022-07-07 14:47 ` [PATCH v13 08/26] ima: Move IMA securityfs files into ima_namespace or onto stack Stefan Berger
2022-07-07 14:47 ` [PATCH v13 09/26] ima: Move ima_lsm_policy_notifier into ima_namespace Stefan Berger
2022-07-07 14:47 ` [PATCH v13 10/26] ima: Switch to lazy lsm policy updates for better performance Stefan Berger
2022-07-07 14:47 ` [PATCH v13 11/26] ima: Define mac_admin_ns_capable() as a wrapper for ns_capable() Stefan Berger
2022-07-07 14:47 ` [PATCH v13 12/26] ima: Only accept AUDIT rules for non-init_ima_ns namespaces for now Stefan Berger
2022-07-07 14:47 ` [PATCH v13 13/26] userns: Add pointer to ima_namespace to user_namespace Stefan Berger
2022-07-07 14:47 ` [PATCH v13 14/26] ima: Implement hierarchical processing of file accesses Stefan Berger
2022-07-07 14:47 ` [PATCH v13 15/26] ima: Implement ima_free_policy_rules() for freeing of an ima_namespace Stefan Berger
2022-07-07 14:47 ` [PATCH v13 16/26] ima: Add functions for creating and " Stefan Berger
2022-07-07 14:47 ` [PATCH v13 17/26] integrity/ima: Define ns_status for storing namespaced iint data Stefan Berger
2022-07-07 14:47 ` Stefan Berger [this message]
2022-07-07 14:47 ` [PATCH v13 19/26] ima: Namespace audit status flags Stefan Berger
2022-07-07 14:47 ` [PATCH v13 20/26] ima: Remove unused iints from the integrity_iint_cache Stefan Berger
2022-07-07 14:47 ` [PATCH v13 21/26] ima: Setup securityfs for IMA namespace Stefan Berger
2022-07-07 14:47 ` [PATCH v13 22/26] ima: Introduce securityfs file to activate an " Stefan Berger
2022-07-07 14:47 ` [PATCH v13 23/26] ima: Show owning user namespace's uid and gid when displaying policy Stefan Berger
2022-07-07 14:47 ` [PATCH v13 24/26] ima: Limit number of policy rules in non-init_ima_ns Stefan Berger
2022-07-07 14:47 ` [PATCH v13 25/26] ima: Restrict informational audit messages to init_ima_ns Stefan Berger
2022-07-07 14:48 ` [PATCH v13 26/26] ima: Enable IMA namespaces Stefan Berger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220707144800.828288-19-stefanb@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=containers@lists.linux.dev \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=jamjoom@us.ibm.com \
    --cc=jejb@linux.ibm.com \
    --cc=jmorris@namei.org \
    --cc=jpenumak@redhat.com \
    --cc=krzysztof.struczynski@huawei.com \
    --cc=lhinds@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lsturman@redhat.com \
    --cc=mpeters@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=puiterwi@redhat.com \
    --cc=rgb@redhat.com \
    --cc=roberto.sassu@huawei.com \
    --cc=serge@hallyn.com \
    --cc=zohar@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).