All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: Andreas Dilger <adilger@Sun.COM>, Brad Boyer <flar@allandria.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	hch@infradead.org, viro@zeniv.linux.org.uk,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] vfs: Add open by file handle support
Date: Mon, 1 Mar 2010 16:25:59 -0500	[thread overview]
Message-ID: <20100301212559.GI23539@fieldses.org> (raw)
In-Reply-To: <5B44BB43-9C50-40CE-AEE2-F2E8662FB5FD@linuxhacker.ru>

On Mon, Mar 01, 2010 at 01:25:56PM -0500, Oleg Drokin wrote:
> Hello!
> 
> On Feb 28, 2010, at 2:00 PM, J. Bruce Fields wrote:
> 
> >> If there is interest to revive this idea, I'll try to dig up the old  
> >> patches we had. I believe that they set a FS_NFS_FSID (or similarly  
> >> named) flag in the file_system_type, and possibly a method that  
> >> extracted this information for NFSd.
> > OK, sure, but if it's only of use to lustre than I don't see how to
> > justify a kernel patch.
> 
> I wonder how does GFS/OCFS2 do this? They cannot depend on the
> SAN block device to have same major:minor on every exporting node, right?

Right, libblkid calculates a uuid from the contents somehow.

> > Another option would be to provide an alternative to
> > nfs-utils/utils/mountd/cache.c's get_uuid() that can request the
> > filesystem's uuid (assuming you've got an easy way to get it from
> > userspace).  That might also save having to add yet another case to e.g.
> > fs/nfsd/nfsfh.c:set_version_and_fsid_type().
> 
> Hopefully there would be a standard way to request the uuid, not
> just a huge switch with separate code for every fstype.

Sure.

--b.

  reply	other threads:[~2010-03-01 21:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19  5:42 [RFC PATCH] Generic name to handle and open by handle syscalls Aneesh Kumar K.V
2010-02-19  5:42 ` [RFC PATCH 1/3] vfs: Add name to file handle conversion support Aneesh Kumar K.V
2010-02-20 18:15   ` Andreas Dilger
2010-02-22  5:15     ` Aneesh Kumar K. V
2010-02-19  5:42 ` [RFC PATCH 2/3] vfs: Add open by file handle support Aneesh Kumar K.V
2010-02-20 18:58   ` Andreas Dilger
2010-02-20 20:13     ` Brad Boyer
     [not found]       ` <FB88A140-C2EB-4E62-9769-D2524C874C8C@sun.com>
2010-02-22  2:46         ` Brad Boyer
2010-02-26 19:21         ` J. Bruce Fields
2010-02-28 17:55           ` Andreas Dilger
2010-02-28 19:00             ` J. Bruce Fields
2010-03-01 18:25               ` Oleg Drokin
2010-03-01 21:25                 ` J. Bruce Fields [this message]
2010-02-22  6:13     ` Aneesh Kumar K. V
2010-02-22  6:31       ` Dave Chinner
2010-02-26 19:24     ` J. Bruce Fields
2010-02-19  5:42 ` [RFC PATCH 3/3] x86: Add new syscalls for x86_32 Aneesh Kumar K.V
2010-02-19  9:34 ` [RFC PATCH] Generic name to handle and open by handle syscalls Andreas Dilger
2010-02-19  9:49   ` Aneesh Kumar K. V
2010-02-20 19:01     ` Andreas Dilger
2010-02-22  6:27       ` Aneesh Kumar K. V
2010-02-22 23:06 ` Jonathan Corbet
2010-02-23  0:56   ` James Morris
2010-02-23  8:58   ` Aneesh Kumar K. V
2010-02-23 19:46     ` Jonathan Corbet
2010-02-24  0:49     ` Dave Chinner
2010-02-25  4:53     ` Serge E. Hallyn
2010-02-25 14:30       ` Jonathan Corbet
2010-02-25 15:19         ` Serge E. Hallyn
2010-02-25 17:55           ` Aneesh Kumar K. V
2010-02-25 18:11             ` Serge E. Hallyn
2010-02-25 18:20               ` Aneesh Kumar K. V
2010-02-25 19:05                 ` Serge E. Hallyn
2010-02-26  9:12                   ` Andreas Dilger
2010-02-26 19:56                     ` Serge E. Hallyn

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=20100301212559.GI23539@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=adilger@Sun.COM \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=flar@allandria.com \
    --cc=green@linuxhacker.ru \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.