lkml.org 
[lkml]   [2018]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] ima,fuse: introduce new fs flag FS_NO_IMA_CACHE
From
Date
> >
> > /*
> > - * 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
> >
>

\
 
 \ /
  Last update: 2018-01-16 12:36    [W:0.042 / U:28.568 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site