[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 2 Feb 2018 17:10:24 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc: Christoph Hellwig <hch@...radead.org>,
linux-integrity@...r.kernel.org,
LSM <linux-security-module@...r.kernel.org>,
linux-fsdevel@...r.kernel.org, Alban Crequy <alban@...volk.io>,
Miklos Szeredi <mszeredi@...hat.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
James Morris <jmorris@...ei.org>,
"Serge E . Hallyn" <serge@...lyn.com>,
Seth Forshee <seth.forshee@...onical.com>,
Dongsu Park <dongsu@...volk.io>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v4 1/2] fuse: introduce new fs_type flag FS_IMA_NO_CACHE
On Fri, Feb 2, 2018 at 4:33 PM, Mimi Zohar <zohar@...ux.vnet.ibm.com> wrote:
> On Fri, 2018-02-02 at 10:20 -0500, Mimi Zohar wrote:
>> Hi Miklos,
>>
>> On Tue, 2018-01-30 at 19:06 +0100, Dongsu Park wrote:
>> > From: Alban Crequy <alban@...volk.io>
>> >
>> > This new fs_type flag FS_IMA_NO_CACHE means files should be re-measured,
>> > re-appraised and re-audited each time. Cached integrity results should
>> > not be used.
>> >
>> > It is useful in FUSE because the userspace FUSE process can change the
>> > underlying files at any time without notifying the kernel.
I don't really have an understanding what IMA is doing, I think the
same thing applies to any network filesystem (i.e. ones with
d_revalidate).
Isn't that the case?
Thanks,
Miklos
Powered by blists - more mailing lists