All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raul Rangel <rrangel@chromium.org>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Eric Snowberg <eric.snowberg@oracle.com>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH v3] ima: detect changes to the backing overlay file
Date: Thu, 26 Oct 2023 09:31:42 -0600	[thread overview]
Message-ID: <CAHQZ30BbtoTGHV803WpiSdCi6Bz9E050FJUy=HEeSAti_zPsqg@mail.gmail.com> (raw)
In-Reply-To: <488442598c3703760ed6182426ed891f85fe0a1a.camel@linux.ibm.com>

On Wed, Oct 25, 2023 at 12:01 PM Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> On Wed, 2023-10-25 at 16:27 +0000, Eric Snowberg wrote:
> >
> > > On Oct 25, 2023, at 8:39 AM, Mimi Zohar <zohar@linux.ibm.com> wrote:
> > >
> > > Commit 18b44bc5a672 ("ovl: Always reevaluate the file signature for
> > > IMA") forced signature re-evaulation on every file access.
> > >
> > > Instead of always re-evaluating the file's integrity, detect a change
> > > to the backing file, by comparing the cached file metadata with the
> > > backing file's metadata.  Verifying just the i_version has not changed
> > > is insufficient.  In addition save and compare the i_ino and s_dev
> > > as well.
> > >
> > > Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> >
> > I ran the file integrity tests that originally uncovered the need for
> > "Commit 18b44bc5a672 ("ovl: Always reevaluate the file signature for
> > IMA”). When the backing file is changed, file integrity remains.  For that
> > part, feel free to add:
> >
> > Tested-by: Eric Snowberg <eric.snowberg@oracle.com>
>
> Thanks!
>
> Mimi
>

I just verified this fixes the speed regression:

```
rrangel920 / # time clang --version >/dev/null

real 0m0.369s
user 0m0.000s
sys 0m0.368s
rrangel920 / #
rrangel920 / # time clang --version >/dev/null

real 0m0.017s
user 0m0.004s
sys 0m0.013s
rrangel920 / # time clang --version >/dev/null

real 0m0.012s
user 0m0.000s
sys 0m0.012s
rrangel920 / # time clang --version >/dev/null

real 0m0.012s
user 0m0.000s
sys 0m0.012s
```

Tested-by: Raul E Rangel <rrangel@chromium.org>

Thanks again for the quick fix!

      reply	other threads:[~2023-10-26 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 14:39 [PATCH v3] ima: detect changes to the backing overlay file Mimi Zohar
2023-10-25 14:59 ` Raul Rangel
2023-10-25 15:09   ` Mimi Zohar
2023-10-25 16:27 ` Eric Snowberg
2023-10-25 18:01   ` Mimi Zohar
2023-10-26 15:31     ` Raul Rangel [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='CAHQZ30BbtoTGHV803WpiSdCi6Bz9E050FJUy=HEeSAti_zPsqg@mail.gmail.com' \
    --to=rrangel@chromium.org \
    --cc=amir73il@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.