From: David Chinner <dgc@sgi.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: dgc@sgi.com, staubach@redhat.com, akpm@linux-foundation.org,
hch@infradead.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] VFS: new fgetattr() file operation
Date: Fri, 26 Oct 2007 09:52:06 +1000 [thread overview]
Message-ID: <20071025235206.GA995458@sgi.com> (raw)
In-Reply-To: <E1IlBqA-0006yj-00@dorka.pomaz.szeredi.hu>
On Fri, Oct 26, 2007 at 01:10:14AM +0200, Miklos Szeredi wrote:
> > On Wed, Oct 24, 2007 at 05:27:04PM +0200, Miklos Szeredi wrote:
> > > > >> Wouldn't you be better off by attempting to implement an "open
> > > > >> by ino" operation and an operation to get the generation count
> > > > >> for the file and then modifying the network protocol of interest
> > > > >> to use these as identifiers for the file to be manipulated?
> > > > >>
> > > > >
> > > > > You mean an "open by inode" on the userspace API? My guess, it
> > > > > wouldn't get very far.
> > > >
> > > > This isn't a new idea and has been implemented on a variety of
> > > > different systems.
> > >
> > > Like?
> >
> > XFS.
> >
> > 'man open_by_handle'
>
> Doesn't seem widely used, with 600 something google hits.
from the man page:
"They are intended for use by a limited set of system utilities such
as backup programs."
It also gets used by HSMs and so it is current, tested and is not
going away....
> And in this
> old thread Linus is not entirely enthusiastic about the concept:
>
> http://lkml.org/lkml/1999/1/11/244
That was "open by inode number", AFAICT. A handle is an opaque
blob that can be an arbitrary length defined by the filesystem.
You have to convert a fd or path to a handle first before you can
use it later, so any filesystem can implement it...
i.e. it is exactly what this (unanswered) post suggested:
http://lkml.org/lkml/1999/1/13/186
Just my 2c worth....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-10-25 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 11:59 Miklos Szeredi
2007-10-24 13:02 ` Peter Staubach
2007-10-24 13:43 ` Miklos Szeredi
2007-10-24 15:02 ` Peter Staubach
2007-10-24 15:27 ` Miklos Szeredi
2007-10-25 22:42 ` David Chinner
2007-10-25 23:10 ` Miklos Szeredi
2007-10-25 23:52 ` David Chinner [this message]
2007-10-26 9:33 ` 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=20071025235206.GA995458@sgi.com \
--to=dgc@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=staubach@redhat.com \
/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®