IMA and fs

[hooanon05]

I have found (at least) two issues about IMA.

1.
Calling stack
- kmem_cache_alloc(iint_cache, GFP_KERNEL)
- ima_inode_alloc()
- inode_init_always()
- xfs_iget_cache_hit()
- xfs_iget()

xfs_iget() holds spinlock before xfs_iget_cache_hit(), and
ima_inode_alloc() cannot use GFP_KERNEL.

2.
ima_path_check() seems to be necessary before every opening a file.
In 2.6.30-rc1, IMA produces lots of messages and stack trace when NFSD
opens a file. 
Does nfsd_open() need to to call ima_path_check()?


J. R. Okajima
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/