From: hooanon05@yahoo.co.jp
To: Mimi Zohar <zohar@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, david safford <safford@watson.ibm.com>
Subject: Re: IMA and fs
Date: Fri, 17 Apr 2009 22:57:46 +0900 [thread overview]
Message-ID: <11555.1239976666@jrobl> (raw)
In-Reply-To: <OF1283DDC6.0AD2926E-ON8525759B.004938DD-8525759B.004A1887@us.ibm.com>
Mimi Zohar:
> > 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.
Yes, the same issue.
I didn't know it was discussed before.
So what is the conclusion? Are you waiting for fixing the spinlock in
xfs?
> > Does nfsd_open() need to to call ima_path_check()?
:::
> Yes, in order for the open/free to be balanced in ima_file_free().
Then how about putting ima_path_check() into __dentry_open() instead of
may_open()?
J. R. Okajima
next prev parent reply other threads:[~2009-04-17 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 13:19 IMA and fs hooanon05
2009-04-17 13:29 ` Mimi Zohar
2009-04-17 13:57 ` hooanon05 [this message]
2009-04-17 18:20 ` Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11555.1239976666@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.com \
--cc=zohar@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox