Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: GUO Zihua <guozihua@huawei.com>,
	linux-integrity@vger.kernel.org, dmitry.kasatkin@gmail.com,
	paul@paul-moore.com
Subject: Re: [PATCH] ima: Handle -ESTALE returned by ima_filter_rule_match()
Date: Thu, 18 Aug 2022 09:43:32 -0400	[thread overview]
Message-ID: <b383f302284dfa31408e2796a9cae60eefd45004.camel@linux.ibm.com> (raw)
In-Reply-To: <20220818020551.18922-1-guozihua@huawei.com>

Hi Scott,

On Thu, 2022-08-18 at 10:05 +0800, GUO Zihua wrote:
> IMA relies on lsm policy update notifier to be notified when it should
> update it's lsm rules.

^IMA relies on the blocking LSM policy notifier callback to update the
LSM based IMA policy 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().

With the lazy LSM policy update, retrying only once was needed.  With
the blocking LSM notifier callback, why is three times needed?  Is this
really a function of how long it takes IMA to walk and update ALL the
LSM based IMA policy rules?  Would having SELinux wait for the -ESTALE
to change do anything?

> 
> Fixes: b16942455193 ("ima: use the lsm policy update notifier")
> Signed-off-by: GUO Zihua <guozihua@huawei.com>

thanks,

Mimi


  reply	other threads:[~2022-08-18 13:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  2:05 [PATCH] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2022-08-18 13:43 ` Mimi Zohar [this message]
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=b383f302284dfa31408e2796a9cae60eefd45004.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=guozihua@huawei.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=paul@paul-moore.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