From: GUO Zihua <guozihua@huawei.com>
To: <linux-integrity@vger.kernel.org>, <zohar@linux.ibm.com>,
<dmitry.kasatkin@gmail.com>, <paul@paul-moore.com>
Subject: [PATCH] ima: Handle -ESTALE returned by ima_filter_rule_match()
Date: Thu, 18 Aug 2022 10:05:51 +0800 [thread overview]
Message-ID: <20220818020551.18922-1-guozihua@huawei.com> (raw)
IMA relies on lsm policy update notifier to be notified when it should
update it's lsm rules.
When SELinux update it's policies, ima would be notified and starts
updating all its lsm rules one-by-one. During this time, -ESTALE would
be returned by ima_filter_rule_match() if it is called with a lsm rule
that has not yet been updated. In ima_match_rules(), -ESTALE is not
handled, and the lsm rule is considered a match, causing extra files
be measured by IMA.
Fix it by retrying for at most three times if -ESTALE is returned by
ima_filter_rule_match().
Fixes: b16942455193 ("ima: use the lsm policy update notifier")
Signed-off-by: GUO Zihua <guozihua@huawei.com>
---
security/integrity/ima/ima_policy.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/security/integrity/ima/ima_policy.c b/security/integrity/ima/ima_policy.c
index a8802b8da946..6edc8cc48dec 100644
--- a/security/integrity/ima/ima_policy.c
+++ b/security/integrity/ima/ima_policy.c
@@ -609,6 +609,7 @@ static bool ima_match_rules(struct ima_rule_entry *rule,
for (i = 0; i < MAX_LSM_RULES; i++) {
int rc = 0;
u32 osid;
+ int retried = 0;
if (!rule->lsm[i].rule) {
if (!rule->lsm[i].args_p)
@@ -616,6 +617,8 @@ static bool ima_match_rules(struct ima_rule_entry *rule,
else
return false;
}
+
+retry:
switch (i) {
case LSM_OBJ_USER:
case LSM_OBJ_ROLE:
@@ -635,6 +638,11 @@ static bool ima_match_rules(struct ima_rule_entry *rule,
default:
break;
}
+
+ if (rc == -ESTALE && retried < 3) {
+ retried++;
+ goto retry;
+ }
if (!rc)
return false;
}
--
2.17.1
next reply other threads:[~2022-08-18 2:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:05 GUO Zihua [this message]
2022-08-18 13:43 ` [PATCH] ima: Handle -ESTALE returned by ima_filter_rule_match() Mimi Zohar
2022-08-19 1:50 ` Guozihua (Scott)
2022-08-22 14:41 ` Mimi Zohar
2022-08-23 8:12 ` Guozihua (Scott)
2022-08-23 13:21 ` Mimi Zohar
2022-08-23 13:28 ` Guozihua (Scott)
2022-08-24 1:26 ` Mimi Zohar
2022-08-24 1:56 ` Guozihua (Scott)
2022-08-25 13:02 ` Mimi Zohar
2022-08-27 9:57 ` Guozihua (Scott)
2022-08-30 1:20 ` Mimi Zohar
2022-08-30 8:41 ` Guozihua (Scott)
2022-08-30 12:03 ` Mimi Zohar
2022-08-30 12:13 ` Guozihua (Scott)
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=20220818020551.18922-1-guozihua@huawei.com \
--to=guozihua@huawei.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=paul@paul-moore.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