From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
jmorris@namei.org, serge@hallyn.com,
zhangliguang@linux.alibaba.com, zhang.jia@linux.alibaba.com
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, tianjia.zhang@linux.alibaba.com
Subject: [PATCH] ima: optimize ima_pcr_extend function by asynchronous
Date: Tue, 14 Apr 2020 19:50:20 +0800 [thread overview]
Message-ID: <20200414115020.99288-1-tianjia.zhang@linux.alibaba.com> (raw)
Because ima_pcr_extend() to operate the TPM chip, this process is
very time-consuming, for IMA, this is a blocking action, especially
when the TPM is in self test state, this process will block for up
to ten seconds.
Because the return result of ima_pcr_extend() is of no concern to IMA,
it only affects the audit of IMA, so this patch use async_schedule()
to asynchronously perform the ima_pcr_extend() operation and do an
audit operation at the end.
In a vtpm scenario, I added the measure policy of BPRM and MMAP to
compare the efficiency before and after applying the patch. The results
show that the overall startup efficiency of conventional processes can
be increased by 5% to 10%. I believe this efficiency increase It will
be more obvious on real hardware tpm.
Signed-off-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
---
security/integrity/ima/ima_queue.c | 80 ++++++++++++++++++++++--------
1 file changed, 59 insertions(+), 21 deletions(-)
diff --git a/security/integrity/ima/ima_queue.c b/security/integrity/ima/ima_queue.c
index 8753212ddb18..12cbf69c2442 100644
--- a/security/integrity/ima/ima_queue.c
+++ b/security/integrity/ima/ima_queue.c
@@ -17,6 +17,7 @@
#include <linux/rculist.h>
#include <linux/slab.h>
+#include <linux/async.h>
#include "ima.h"
#define AUDIT_CAUSE_LEN_MAX 32
@@ -151,6 +152,42 @@ static int ima_pcr_extend(const u8 *hash, int pcr)
return result;
}
+struct ima_pcr_extend_async_ctx {
+ struct ima_template_entry *entry;
+ int violation;
+ const char *op;
+ struct inode *inode;
+ const unsigned char *filename;
+ const char *audit_cause;
+ int audit_info;
+ int result;
+};
+
+static void ima_pcr_extend_async(void *data, async_cookie_t cookie)
+{
+ struct ima_pcr_extend_async_ctx *ctx = data;
+ u8 digest[TPM_DIGEST_SIZE];
+ char tpm_audit_cause[AUDIT_CAUSE_LEN_MAX];
+ int result;
+
+ if (ctx->violation) /* invalidate pcr */
+ memset(digest, 0xff, sizeof(digest));
+ else
+ memcpy(digest, ctx->entry->digest, sizeof(digest));
+
+ result = ima_pcr_extend(digest, ctx->entry->pcr);
+ if (result != 0) {
+ snprintf(tpm_audit_cause, AUDIT_CAUSE_LEN_MAX, "TPM_error(%d)",
+ result);
+ ctx->audit_cause = tpm_audit_cause;
+ ctx->audit_info = 0;
+ }
+ integrity_audit_msg(AUDIT_INTEGRITY_PCR, ctx->inode, ctx->filename,
+ ctx->op, ctx->audit_cause, ctx->result, ctx->audit_info);
+
+ kfree(ctx);
+}
+
/*
* Add template entry to the measurement list and hash table, and
* extend the pcr.
@@ -163,20 +200,16 @@ int ima_add_template_entry(struct ima_template_entry *entry, int violation,
const char *op, struct inode *inode,
const unsigned char *filename)
{
- u8 digest[TPM_DIGEST_SIZE];
const char *audit_cause = "hash_added";
- char tpm_audit_cause[AUDIT_CAUSE_LEN_MAX];
int audit_info = 1;
- int result = 0, tpmresult = 0;
+ int result = 0;
+ struct ima_pcr_extend_async_ctx *ctx;
mutex_lock(&ima_extend_list_mutex);
- if (!violation) {
- memcpy(digest, entry->digest, sizeof(digest));
- if (ima_lookup_digest_entry(digest, entry->pcr)) {
- audit_cause = "hash_exists";
- result = -EEXIST;
- goto out;
- }
+ if (!violation && ima_lookup_digest_entry(entry->digest, entry->pcr)) {
+ audit_cause = "hash_exists";
+ result = -EEXIST;
+ goto out;
}
result = ima_add_digest_entry(entry, 1);
@@ -186,20 +219,25 @@ int ima_add_template_entry(struct ima_template_entry *entry, int violation,
goto out;
}
- if (violation) /* invalidate pcr */
- memset(digest, 0xff, sizeof(digest));
-
- tpmresult = ima_pcr_extend(digest, entry->pcr);
- if (tpmresult != 0) {
- snprintf(tpm_audit_cause, AUDIT_CAUSE_LEN_MAX, "TPM_error(%d)",
- tpmresult);
- audit_cause = tpm_audit_cause;
- audit_info = 0;
+ ctx = kmalloc(sizeof(*ctx), GFP_KERNEL);
+ if (!ctx) {
+ audit_cause = "ENOMEM";
+ result = -ENOMEM;
+ goto out;
}
+
+ ctx->entry = entry;
+ ctx->violation = violation;
+ ctx->op = op;
+ ctx->inode = inode;
+ ctx->filename = filename;
+ ctx->audit_cause = audit_cause;
+ ctx->audit_info = audit_info;
+ ctx->result = result;
+ async_schedule(ima_pcr_extend_async, ctx);
+
out:
mutex_unlock(&ima_extend_list_mutex);
- integrity_audit_msg(AUDIT_INTEGRITY_PCR, inode, filename,
- op, audit_cause, result, audit_info);
return result;
}
--
2.17.1
next reply other threads:[~2020-04-14 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 11:50 Tianjia Zhang [this message]
2020-04-14 16:11 ` Mimi Zohar
2020-04-14 18:07 ` Ken Goldman
2020-04-15 2:53 ` Tianjia Zhang
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=20200414115020.99288-1-tianjia.zhang@linux.alibaba.com \
--to=tianjia.zhang@linux.alibaba.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=zhang.jia@linux.alibaba.com \
--cc=zhangliguang@linux.alibaba.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
all inboxes | Powered by JetHome®