From: Shaya Potter <spotter@cs.columbia.edu>
To: crispin@crispincowan.com
Cc: Kentaro Takeda <takedakn@nttdata.co.jp>,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>,
Chris Wright <chrisw@sous-sol.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Toshiharu Harada <haradats@nttdata.co.jp>,
Andrew Morton <akpm@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [TOMOYO #11 (linux-next) 01/11] Introduce new LSM hooks where vfsmount is available.
Date: Thu, 23 Oct 2008 13:57:34 -0400 [thread overview]
Message-ID: <4900BB0E.9000303@cs.columbia.edu> (raw)
In-Reply-To: <48FCF6CA.2060406@cs.columbia.edu>
Shaya Potter wrote:
> crispin@crispincowan.com wrote:
>> Quoting Shaya Potter <spotter@cs.columbia.edu>:
>>> I know I'm late to the game in this, but as I recently asked about this
>>> and didn't get an answer, I'll re-ask my approach.
>>>
>>> Why can't you do this
>>>
>>> in lookup()
>>>
>>> - resolve rules (not for single process, but for all processes) for
>>> said path and tag dentry (seem to already have a hook)
>>>
>>> in permission()
>>
>> Because it doesn't work
>> http://kerneltrap.org/mailarchive/linux-fsdevel/2007/6/8/319446
>>
>> Quick summary: The difference between the pathname model and the label
>> model is dynamism. The accessi really is determined by the pathname to
>> the file that you used to access the file. If you try to compute
>> access based on attributes tagged onto the file, then you have to
>> re-compute those attributes every time someone renames a file.
>
> ok. simple question then so why not just recompute them every every
> rename? are rename's that common relative to all other file operations
> where we care?
just want to followup as didn't get a response. If the problem is
rename(), what's the problem with dropping the label on rename() to
force a reevaluation on the next pass through the lookup() code.
next prev parent reply other threads:[~2008-10-23 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 7:34 [TOMOYO #11 (linux-next) 00/11] TOMOYO Linux Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 01/11] Introduce new LSM hooks where vfsmount is available Kentaro Takeda
2008-10-20 12:27 ` Shaya Potter
2008-10-20 19:34 ` crispin
2008-10-20 21:23 ` Shaya Potter
2008-10-23 17:57 ` Shaya Potter [this message]
2008-10-20 16:44 ` Miklos Szeredi
2008-10-21 5:09 ` Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 02/11] Add in_execve flag into task_struct Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 03/11] Singly linked list implementation Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 04/11] Introduce d_realpath() Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 05/11] Memory and pathname management functions Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 06/11] Common functions for TOMOYO Linux Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 07/11] File operation restriction part Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 08/11] Domain transition handler Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 09/11] LSM adapter functions Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 10/11] Kconfig and Makefile Kentaro Takeda
2008-10-20 7:34 ` [TOMOYO #11 (linux-next) 11/11] MAINTAINERS info Kentaro Takeda
2008-10-27 2:18 ` [TOMOYO #11 (linux-next) 00/11] TOMOYO Linux Kentaro Takeda
2008-10-29 19:18 ` Serge E. Hallyn
2008-10-30 5:27 ` Toshiharu Harada
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=4900BB0E.9000303@cs.columbia.edu \
--to=spotter@cs.columbia.edu \
--cc=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=chrisw@sous-sol.org \
--cc=crispin@crispincowan.com \
--cc=haradats@nttdata.co.jp \
--cc=hch@lst.de \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=serue@us.ibm.com \
--cc=takedakn@nttdata.co.jp \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome