On Mon, 2010-10-18 at 21:16 -0400, Eric Paris wrote:
> IMA currently alocated an inode integrity structure for every inode in
> core. This stucture is about 120 bytes long. Most files however
> (especially on a system which doesn't make use of IMA) will never need any
> of this space. The problem is that if IMA is enabled we need to know
> information about the number of readers and the number of writers for every
> inode on the box. At the moment we collect that information in the per
> inode iint structure and waste the rest of the space. This patch moves those
> counters into the struct inode so we can eventually stop allocating an IMA
> integrity structure except when absolutely needed.
>
> This patch does the minimum needed to move the location of the data. Further
> cleanups, especially the location of counter updates, may still be possible.
>
> Signed-off-by: Eric Paris <eparis@xxxxxxxxxx>
Noone should apply this, it doesn't build on !CONFIG_IMA. Notice my
extra ; on the end of the line :(
> +static inline void ima_check_counters(struct inode *inode);
> +{
> + return;
> +}
> #endif /* CONFIG_IMA_H */
> #endif /* _LINUX_IMA_H */
--
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
