From: Christoph Hellwig <hch@infradead.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: hch@infradead.org, 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: Wed, 7 Nov 2007 22:45:23 +0000 [thread overview]
Message-ID: <20071107224523.GA8223@infradead.org> (raw)
In-Reply-To: <200711080704.CHC65673.OOtFJFFSHQVOML@I-love.SAKURA.ne.jp>
On Thu, Nov 08, 2007 at 07:04:23AM +0900, Tetsuo Handa wrote:
> The reason why I want to access namespace_sem inside security_inode_create() is that
> it doesn't receive "struct vfsmount" parameter.
> If "struct vfsmount" *were* passed to security_inode_create(),
> I have no need to access namespace_sem.
Same argument as with the AA folks: it does not have any business looking
at the vfsmount. If you create a file it can and in many setups will
show up in multiple vfsmounts, so making decisions based on the particular
one this creat happens through is wrong and actually dangerous.
next prev parent reply other threads:[~2007-11-07 22:45 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
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 [this message]
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=20071107224523.GA8223@infradead.org \
--to=hch@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