From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Morton <akpm@osdl.org>, Oleg Drokin <green@linuxhacker.ru>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: FMODE_EXEC or alike?
Date: Wed, 22 Feb 2006 18:31:52 -0500 [thread overview]
Message-ID: <20060222233152.GF11556@fieldses.org> (raw)
In-Reply-To: <1140646653.7879.25.camel@lade.trondhjem.org>
On Wed, Feb 22, 2006 at 05:17:33PM -0500, Trond Myklebust wrote:
> I understand FMODE_EXEC to mean that we want to call
> deny_write_access(). OTOH, FMODE_WRITE is supposed to trigger an
> automatic call to get_write_access().
Ugh. OK, well that makes FMODE_EXEC useless for the server, then.
It'd be nice to be able to give the server some way of enforcing the
deny bits. Otherwise, though translating FMODE_EXEC to DENY_WRITE will
at least allow the nfs server to deny writes by other clients, it'll
still do nothing to protect against writers on the exported filesystem
(even local writers--nevermind the cluster case).
And an open flag is attractive since it gives at least some hope that we
might be able to do DENY_WRITE atomically with the open. Samba
apparently just does the open and then tries to get a mandatory lock
afterwards, but that seems racy.
--b.
next prev parent reply other threads:[~2006-02-22 23:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 22:19 FMODE_EXEC or alike? Oleg Drokin
2006-02-21 5:51 ` Andrew Morton
2006-02-21 11:30 ` Oleg Drokin
2006-02-21 11:36 ` Andrew Morton
2006-02-21 11:56 ` Oleg Drokin
2006-02-21 13:59 ` Trond Myklebust
2006-02-21 14:15 ` Antonio Vargas
2006-02-21 14:21 ` Oleg Drokin
2006-02-22 9:57 ` Antonio Vargas
2006-02-21 14:42 ` Trond Myklebust
2006-02-21 23:26 ` J. Bruce Fields
2006-02-21 23:32 ` Trond Myklebust
2006-02-22 19:57 ` J. Bruce Fields
2006-02-22 21:36 ` Trond Myklebust
2006-02-22 22:04 ` J. Bruce Fields
2006-02-22 22:17 ` Trond Myklebust
2006-02-22 23:31 ` J. Bruce Fields [this message]
2006-02-21 10:39 ` Christoph Hellwig
2006-02-22 1:03 ` Chris Wedgwood
2006-02-22 8:59 ` Steven Whitehouse
2006-02-22 21:42 ` J. Bruce Fields
2006-02-22 22:02 ` Christoph Hellwig
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=20060222233152.GF11556@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@osdl.org \
--cc=green@linuxhacker.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.