Messages in this thread | | | Subject | Re: IMA and fs | From | Mimi Zohar <> | Date | Fri, 17 Apr 2009 09:29:19 -0400 |
| |
hooanon05@yahoo.co.jp wrote on 04/16/2009 09:19:45 AM:
> 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.
This looks similar to the xfs - IMA problem discussed http://lkml.org/lkml/2009/2/20/327.
> 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
Yes, in order for the open/free to be balanced in ima_file_free().
Mimi Zohar
| |