From: Jamie Lokier <jamie@shareable.org>
To: Andreas Dilger <adilger@sun.com>
Cc: Valdis.Kletnieks@vt.edu,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Andreas Gruenbacher <agruen@suse.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfs: new O_NODE open flag
Date: Mon, 28 Sep 2009 16:53:53 +0100 [thread overview]
Message-ID: <20090928155353.GA25375@shareable.org> (raw)
In-Reply-To: <20090925190222.GX10562@webber.adilger.int>
Andreas Dilger wrote:
> > It's not possible even without this flag. Consider:
> >
> > fd1 = open("/tmp/foo",flags);
> > rc = rename("/tmp/foo","/tmp/bar");
> > fd2 = open("/tmp/foo",flags);
> >
> > Or were you asking if *absent that sort of tomfoolery* if it would work?
>
> No, the point is that we HAVE an fd that points to the original "/tmp/foo"
> opened with O_NODE, and now (after an ioctl, stat, etc) we decide it is
> safe to open the file read and/or write without releasing the existing
> fd. The whole point is to AVOID this kind of tomfoolery.
Make sense, and openat() seems like a good way to accomplish it.
-- Jamie
prev parent reply other threads:[~2009-09-28 15:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 14:51 [PATCH] vfs: new O_NODE open flag Miklos Szeredi
2009-09-25 0:23 ` Andreas Gruenbacher
2009-09-25 5:52 ` Miklos Szeredi
2009-09-25 12:37 ` Dr. David Alan Gilbert
2009-09-25 12:18 ` Miklos Szeredi
2009-09-25 17:08 ` Jamie Lokier
2009-09-25 16:53 ` Andreas Dilger
2009-09-25 17:20 ` Valdis.Kletnieks
2009-09-25 18:35 ` Dr. David Alan Gilbert
2009-09-25 21:18 ` Valdis.Kletnieks
2009-09-28 10:25 ` Miklos Szeredi
2009-09-28 13:28 ` Jamie Lokier
2009-09-28 14:07 ` Miklos Szeredi
2009-09-28 14:10 ` Jamie Lokier
2009-09-30 8:18 ` Florian Weimer
2009-09-28 15:21 ` Andreas Dilger
2009-09-28 16:04 ` Miklos Szeredi
2009-10-04 19:03 ` Pavel Machek
2009-10-04 22:58 ` Jamie Lokier
2009-10-23 17:10 ` /proc filesystem allows bypassing directory permissions on Linux (was Re: [PATCH] vfs: new O_NODE open flag) Pavel Machek
2009-10-14 13:14 ` [PATCH] vfs: new O_NODE open flag Andreas Gruenbacher
2009-09-25 19:02 ` Andreas Dilger
2009-09-28 15:53 ` Jamie Lokier [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=20090928155353.GA25375@shareable.org \
--to=jamie@shareable.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=adilger@sun.com \
--cc=agruen@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=miklos@szeredi.hu \
/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).