On Tue, Dec 11, 2012 at 1:18 PM, Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx> wrote: > The appraisal policy is based on the object metadata, such as the uid, > so the result is static and can be cached. The measurement policy, on > the other hand, is normally based on the subject (eg. who is > reading/executing) the file. Knowledge of whether the file has been > measured is cached in the iint, but unlike the appraisal policy, not > whether it needs to be measured. Having the flag on a per inode basis, > doesn't really help. Can you try again? Even I can't parse this. Not sure what to tell you to try again, maybe give us a summary at a high level again and then why this patch is specifically necessary? -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
