linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonio Vargas" <windenntw@gmail.com>
To: "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 10:57:24 +0100	[thread overview]
Message-ID: <69304d110602220157i71a1455cped625a19205cc4a7@mail.gmail.com> (raw)
In-Reply-To: <20060221142159.GI5733@linuxhacker.ru>

On 2/21/06, Oleg Drokin <green@linuxhacker.ru> wrote:
> Hello!
>
> On Tue, Feb 21, 2006 at 03:15:53PM +0100, Antonio Vargas wrote:
> > > > We would need to understand whether this is needed by other distributed
> > > > filesystems and if so, whether the proposed implementation is suitable and
> > > > sufficient.
> > > Hmm.... We might possibly want to use that for NFSv4 at some point in
> > > order to deny write access to the file to other clients while it is in
> > > use.
> > When done with regards to failing a write if anyone has mapped the
> > file for executing it, or failing the execute if it's open/mmaped for
> > write, I can't really see the difference between local, remote and
> > clustered filesystems...
>
> Currently this is only possible locally, when both execution and opening
> for writing is performed on the same node. Then VFS enforces ETXTBSY.
> But if you do exec on one node and open for writing on another,
> VFSes on those nodes have no idea on what happens on all other nodes.
>

Thanks for the enlightement Oleg, I had assumed the owner of the file
to write over the executable while it's being executed... sort of
self-modifying code, but s/self/external/ ;)

Greetz, Antonio Vargas aka winden of network

  reply	other threads:[~2006-02-22  9:57 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 [this message]
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
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=69304d110602220157i71a1455cped625a19205cc4a7@mail.gmail.com \
    --to=windenntw@gmail.com \
    --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).