[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b74a9a3edc52d96a7a34d6ba327fdb2a5a79a80d.camel@linux.ibm.com>
Date: Mon, 15 Apr 2024 06:47:12 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Miklos Szeredi <miklos@...redi.hu>, Stefan Berger <stefanb@...ux.ibm.com>
Cc: Amir Goldstein <amir73il@...il.com>, linux-integrity@...r.kernel.org,
linux-unionfs@...r.kernel.org, linux-kernel@...r.kernel.org,
roberto.sassu@...wei.com, Christian Brauner <brauner@...nel.org>
Subject: Re: [RFC 2/2] ima: Fix detection of read/write violations on
stacked filesystems
On Mon, 2024-04-15 at 10:09 +0200, Miklos Szeredi wrote:
> On Fri, 12 Apr 2024 at 21:09, Stefan Berger <stefanb@...ux.ibm.com> wrote:
>
> > I was hoping that this would be sufficiently generic to work with
> > potential future stacked filesystems as well that would need to also
> > provide support for D_REAL_FILEDATA.
>
> I also have very bad feelings from IMA digging in the internals of overlayfs.
>
> We should strive to get rid of remaining d_real() instances, not add more.
>
> On a related note, D_REAL_METADATA was apparently added for IMA
> (commit 11b3f8ae7081 ("fs: remove the inode argument to ->d_real()
> method")), but there's no current user. What's up with this?
It's queued in
https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git/ next-
integrity branch and should be linux-next.
thanks,
Mimi
Powered by blists - more mailing lists