From: Mimi Zohar <zohar@linux.ibm.com>
To: Sahil Gupta <s.gupta@arista.com>
Cc: Danny Hu <dannyhu@arista.com>,
linux-integrity@vger.kernel.org, Julien Gomes <julien@arista.com>,
Pierre De Abreu <pierre@arista.com>,
Kunal Bharathi <kbharathi@arista.com>
Subject: Re: IMA: Avoid redundant rehashing on stacked filesystems backed by structurally immutable filesystems
Date: Fri, 01 May 2026 07:42:48 -0400 [thread overview]
Message-ID: <4cbd1b20680e2dceba8870f62f2081c333113192.camel@linux.ibm.com> (raw)
In-Reply-To: <CABEuK14__XuRO2KOd3w+qx5_nw4iB2yPcF2R68a09A4hcJkyFw@mail.gmail.com>
On Thu, 2026-04-30 at 21:32 -0500, Sahil Gupta wrote:
> > Have you considered using IS_RDONLY(real_inode)?
>
> OOC are ima caches invalidated on fs reconfigure? If that is the case,
> then IS_RDONLY ought to do the trick.
Per-inode IMA integrity status (iint) is now stored directly in the inode's LSM
security blob rather than in a red-black tree cache. By "fs reconfiguration",
do you mean remounting the filesystem? If so, the iint stored in the LSM
security blob should be freed when the filesystem is unmounted.
Mimi
next prev parent reply other threads:[~2026-05-01 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 23:55 IMA: Avoid redundant rehashing on stacked filesystems backed by structurally immutable filesystems Danny Hu
2026-05-01 2:29 ` Mimi Zohar
2026-05-01 2:32 ` Sahil Gupta
2026-05-01 11:42 ` Mimi Zohar [this message]
2026-05-01 16:02 ` Sahil Gupta
2026-05-01 16:16 ` Danny Hu
2026-05-01 19:48 ` Mimi Zohar
2026-05-01 20:05 ` Sahil Gupta
2026-05-01 20:22 ` Danny Hu
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=4cbd1b20680e2dceba8870f62f2081c333113192.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dannyhu@arista.com \
--cc=julien@arista.com \
--cc=kbharathi@arista.com \
--cc=linux-integrity@vger.kernel.org \
--cc=pierre@arista.com \
--cc=s.gupta@arista.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