From: Mimi Zohar <zohar@linux.ibm.com>
To: GUO Zihua <guozihua@huawei.com>,
dmitry.kasatkin@gmail.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com
Cc: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH v4 2/2] ima: Handle -ESTALE returned by ima_filter_rule_match()
Date: Mon, 19 Sep 2022 17:35:05 -0400 [thread overview]
Message-ID: <8ed58a588b80e6bcad13fa32b4fca22cbda66f38.camel@linux.ibm.com> (raw)
In-Reply-To: <20220909011516.55957-3-guozihua@huawei.com>
Hi Scott,
> @@ -612,6 +614,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:
> @@ -631,10 +635,28 @@ static bool ima_match_rules(struct ima_rule_entry *rule,
> default:
> break;
> }
> - if (!rc)
> - return false;
> +
> + if (rc == -ESTALE) {
> + rule = ima_lsm_copy_rule(rule);
Re-using rule here
> + if (rule) {
and here doesn't look right.
> + rule_reinitialized = true;
> + goto retry;
> + }
> + }
> + if (!rc) {
> + result = false;
> + goto out;
> + }
> }
> - return true;
> + result = true;
> +
> +out:
> + if (rule_reinitialized) {
> + for (i = 0; i < MAX_LSM_RULES; i++)
> + ima_filter_rule_free(rule->lsm[i].rule);
> + kfree(rule);
> + }
Shouldn't freeing the memory be immediately after the retry?
Otherwise, only the last instance of processing -ESTALE would be freed.
> + return result;
> }
>
> /*
--
thanks,
Mimi
next prev parent reply other threads:[~2022-09-19 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 1:15 [PATCH v4 0/2] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2022-09-09 1:15 ` [PATCH v4 1/2] ima: Simplify ima_lsm_copy_rule GUO Zihua
2022-09-19 21:35 ` Mimi Zohar
2022-09-09 1:15 ` [PATCH v4 2/2] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2022-09-19 21:35 ` Mimi Zohar [this message]
2022-09-21 12:36 ` 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=8ed58a588b80e6bcad13fa32b4fca22cbda66f38.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=guozihua@huawei.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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).