Messages in this thread | | | From | hooanon05@yahoo ... | Subject | IMA and fs | Date | Thu, 16 Apr 2009 22:19:45 +0900 |
| |
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
| |