From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] atomic open(..., O_CREAT | ...)
Date: Mon, 08 Aug 2005 18:58:46 -0400 [thread overview]
Message-ID: <1123541926.8249.8.camel@lade.trondhjem.org> (raw)
In-Reply-To: <E1E2G68-0006H2-00@dorka.pomaz.szeredi.hu>
ty den 09.08.2005 Klokka 00:27 (+0200) skreiv Miklos Szeredi:
> I'd like to make my filesystem be able to do file creation and opening
> atomically. This is needed for filesystems which cannot separate
> checking open permission from the actual open operation.
>
> Usually any filesystem served from userspace by an unprivileged (no
> CAP_DAC_OVERRIDE) process will be such (ftp, sftp, etc.).
>
> With nameidata->intent.open.* it is possible to do the actual open
> from ->lookup() or ->create(). However there's no easy way to
> associate the 'struct file *' returned by dentry_open() with the
> filesystem's private file object. Also if there's some error after
> the file has been opened but before a successful return of the file
> pointer, the filesystem has no way to know that it should destroy the
> private file object.
We've already got a patch that does this, and that I'm queueing up for
inclusion. See
http://client.linux-nfs.org/Linux-2.6.x/2.6.12/linux-2.6.12-63-open_file_intents.dif
As for the "orig flags" thing. What is the point of that?
Cheers,
Trond
next prev parent reply other threads:[~2005-08-08 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 22:27 Miklos Szeredi
2005-08-08 22:58 ` Trond Myklebust [this message]
2005-08-09 7:46 ` Miklos Szeredi
2005-08-09 13:34 ` Trond Myklebust
2005-08-09 15:47 ` Bryan Henderson
2005-08-09 16:07 ` Trond Myklebust
2005-08-09 16:34 ` Bryan Henderson
2005-08-09 16:40 ` Miklos Szeredi
2005-08-09 17:18 ` Trond Myklebust
2005-08-09 17:44 ` Miklos Szeredi
2005-08-09 18:38 ` Trond Myklebust
2005-08-09 20:42 ` Miklos Szeredi
2005-08-09 21:11 ` Trond Myklebust
2005-08-09 21:19 ` Miklos Szeredi
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=1123541926.8249.8.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®