From: Mimi Zohar <zohar@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
linux-integrity@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 1/2] ima: don't access a file's integrity status before an IMA policy is loaded
Date: Mon, 22 Mar 2021 14:02:27 -0400 [thread overview]
Message-ID: <92d2e1860d209fe22f8ae5696fc9496e15dd2b31.camel@linux.ibm.com> (raw)
In-Reply-To: <YFjLG7+mhDgsQOYu@gmail.com>
On Mon, 2021-03-22 at 09:51 -0700, Eric Biggers wrote:
> On Mon, Mar 22, 2021 at 11:42:06AM -0400, Mimi Zohar wrote:
> > Only after an IMA policy is loaded, check, save, or update the cached
> > file's integrity status.
> >
> > Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
>
> This commit message doesn't describe what the actual effect of this change is.
> Is it fixing something?
No, it's just short circuiting out even earlier, but isn't needed.
Mimi
prev parent reply other threads:[~2021-03-22 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 15:42 [PATCH 1/2] ima: don't access a file's integrity status before an IMA policy is loaded Mimi Zohar
2021-03-22 15:42 ` [PATCH 2/2] integrity: double check iint_cache was initialized Mimi Zohar
2021-03-22 16:52 ` Eric Biggers
2021-03-22 18:02 ` Mimi Zohar
2022-02-24 14:20 ` Petr Vorel
2022-02-24 17:32 ` Casey Schaufler
2022-02-24 17:42 ` Petr Vorel
2022-02-24 18:51 ` Casey Schaufler
2022-02-25 19:58 ` Mimi Zohar
2022-02-28 13:44 ` Petr Vorel
2022-02-28 16:48 ` Mimi Zohar
2021-03-22 16:51 ` [PATCH 1/2] ima: don't access a file's integrity status before an IMA policy is loaded Eric Biggers
2021-03-22 18:02 ` Mimi Zohar [this message]
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=92d2e1860d209fe22f8ae5696fc9496e15dd2b31.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dvyukov@google.com \
--cc=ebiggers@kernel.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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).