Thread (3 messages) 3 messages, 3 authors, 2018-01-16

[PATCH] ima,fuse: introduce new fs flag FS_NO_IMA_CACHE

From: Mimi Zohar <hidden>
Date: 2018-01-16 11:35:45
Also in: linux-integrity, lkml

quoted
        /*
-        * 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
quoted
        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
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help