>>>>> "Eric" == Eric Paris <eparis@xxxxxxxxxx> writes: Eric> On Mon, 2010-10-25 at 15:21 -0400, John Stoffel wrote: >> >>>>> "Eric" == Eric Paris <eparis@xxxxxxxxxx> writes: >> Which seems to fly in the face of your claim that it needs to be able >> to re-enable itself by tracking open inodes even when disabled. Eric> You're confusing multiple completely unrelated things. Your Eric> confusing loading an IMA measurement policy vs IMA indicating Eric> that it's measurements may be unreliable. So educate me (and the rest of LKML) about these differences and what they mean. Can you please add in a patch to this series which puts in some documentation on how and why to use this stuff? And can you also change the Kconfig to default to 'N' for this feature too! The help text says to say 'N' by default, so that should be the default, right? >> As the number of inodes goes up (say during a backup which reads >> them...) won't the size of this cache go up as well, even when IMA is >> disabled? Why is this overhead even needed? Eric> At the end of this patch the number of integrity structures Eric> still has a 1-1 mapping with the number of inodes. If you look Eric> at the entire series you will see that is not the case. Eric> This patch by itself will cut the memory usage per inode by Eric> almost 600 bytes. That's a good thing then. John -- 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
