From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "J. Bruce Fields" <bfields@fieldses.org>
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 17:17:33 -0500 [thread overview]
Message-ID: <1140646653.7879.25.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20060222220435.GJ28219@fieldses.org>
On Wed, 2006-02-22 at 17:04 -0500, J. Bruce Fields wrote:
> What I don't understand is the source of the requirement that
> FMODE_WRITE|FMODE_EXEC opens be disallowed.
>
> The only users of FMODE_EXEC introduced by Oleg's patch use a hardcoded
> FMODE_READ|FMODE_EXEC, so it doesn't seem to impose any constraints on
> the meaning of FMODE_WRITE|FMODE_EXEC.
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().
Those two calls are mutually exclusive.
Cheers,
Trond
next prev parent reply other threads:[~2006-02-22 22:17 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 [this message]
2006-02-22 23:31 ` J. Bruce Fields
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=1140646653.7879.25.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=green@linuxhacker.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).