From: Toshiharu Harada <haradats@nttdata.co.jp>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
crispin@crispincowan.com
Subject: Re: Problem with accessing namespace_sem from LSM.
Date: Tue, 06 Nov 2007 16:18:21 +0900 [thread overview]
Message-ID: <4730153D.6040200@nttdata.co.jp> (raw)
In-Reply-To: <20071105201126.6b58bbd1@laptopd505.fenrus.org>
On 11/6/2007 1:11 PM, Arjan van de Ven wrote:
> On Tue, 06 Nov 2007 13:00:41 +0900
> Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote:
>
>> Hello.
>>
>> I found that accessing namespace_sem from security_inode_create()
>> causes lockdep warning when compiled with CONFIG_PROVE_LOCKING=y .
>
> sounds like you have an AB-BA deadlock...
sed /you/AppArmor shipped with OpenSuSE 10.1 and 10.2/ :)
Though I don't think this deadlock should occur quite often,
it occurs when it occurs. Care should be taken promptly.
There should be no way around for this problem as its nature.
Passing vfsmount parameter to VFS helper functions and
LSM hooks seems to be a good choice to me.
Cheers,
Toshiharu Harada
next prev parent reply other threads:[~2007-11-06 7:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 4:00 Problem with accessing namespace_sem from LSM Tetsuo Handa
2007-11-06 4:11 ` Arjan van de Ven
2007-11-06 7:18 ` Toshiharu Harada [this message]
2007-11-06 13:35 ` Christoph Hellwig
2007-11-06 14:52 ` Tetsuo Handa
2007-11-07 17:30 ` Christoph Hellwig
2007-11-07 22:04 ` Tetsuo Handa
2007-11-07 22:45 ` Christoph Hellwig
2007-11-08 0:14 ` Tetsuo Handa
2007-11-08 18:58 ` Crispin Cowan
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=4730153D.6040200@nttdata.co.jp \
--to=haradats@nttdata.co.jp \
--cc=arjan@infradead.org \
--cc=crispin@crispincowan.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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