lkml.org 
[lkml]   [2009]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: IMA and fs
From
Date
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


\
 
 \ /
  Last update: 2009-04-17 15:31    [W:0.257 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site