From: Christoph Hellwig <hch@lst.de>
To: Alex Zarochentsev <zam@namesys.com>
Cc: Christoph Hellwig <hch@lst.de>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix reiser4 compilation for ->permission changes
Date: Mon, 13 Sep 2004 19:19:17 +0200 [thread overview]
Message-ID: <20040913171916.GA26997@lst.de> (raw)
In-Reply-To: <20040913170911.GB27411@backtop.namesys.com>
On Mon, Sep 13, 2004 at 09:09:11PM +0400, Alex Zarochentsev wrote:
> > ->permission is the only access checking method for filesystems,
> > everything else is supposed to happen through LSM which may use xattr
> > storage in the filesystem.
>
> I think what reiser4 needs is exactly the fs-specific per-object permission
> check. Is i_op->permission() going to be obsolete? If not, ->permission()
> is the best (available) way to call reiser4 permission plugin methods.
Currently there is no permission checking in reiser4 that's different
from generic_permission so don't set a ->permission. If you ever have
more checking set it for those objects that want more checking instead
of such a useless indirection.
prev parent reply other threads:[~2004-09-13 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 14:02 [PATCH] fix reiser4 compilation for ->permission changes Christoph Hellwig
2004-09-13 14:04 ` Christoph Hellwig
2004-09-13 17:09 ` Alex Zarochentsev
2004-09-13 17:19 ` Christoph Hellwig [this message]
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=20040913171916.GA26997@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zam@namesys.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