[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1516102534.6607.103.camel@linux.vnet.ibm.com>
Date: Tue, 16 Jan 2018 06:35:34 -0500
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: Alban Crequy <alban@...volk.io>,
Alban Crequy <alban.crequy@...il.com>
Cc: Iago López Galeiras <iago@...volk.io>,
Dongsu Park <dongsu@...volk.io>,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, Miklos Szeredi <miklos@...redi.hu>,
Seth Forshee <seth.forshee@...onical.com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH] ima,fuse: introduce new fs flag FS_NO_IMA_CACHE
> >
> > /*
> > - * Reset the measure, appraise and audit cached flags either if
> > - * ima_inode_setxattr was called or based on policy, forcing
> > - * the file to be re-evaluated.
> > + * Reset the measure, appraise and audit cached flags either if:
> > + * - ima_inode_setxattr was called, or
> > + * - based on policy ("force"), or
> > + * - based on filesystem feature flag
> > + * forcing the file to be re-evaluated.
> > */
>
> Now that I think about it, it's also possible to write this patch
> without basing it on Mimi's patch "ima: define a new policy option
> named force", which is not in next-integrity yet. Should I try that?
Yes, thank you. As you're proposing a new flag, please remember to Cc
the fsdevel mailing list as well.
Mimi
>
> > if (test_and_clear_bit(IMA_CHANGE_XATTR, &iint->atomic_flags)) {
> > iint->flags &= ~IMA_DONE_MASK;
> > - } else if (action & IMA_FORCE) {
> > + } else if (action & IMA_FORCE || inode->i_sb->s_type->fs_flags & FS_NO_IMA_CACHE) {
> > if (action & IMA_MEASURE) {
> > iint->measured_pcrs = 0;
> > iint->flags &=
> > --
> > 2.13.6
> >
>
Powered by blists - more mailing lists