linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.de>
Cc: Boaz Harrosh <openosd@gmail.com>, NFS <linux-nfs@vger.kernel.org>
Subject: Re: Should exportfs/mountd cope with case-insensitive directory names.
Date: Fri, 4 Apr 2014 10:34:13 -0400	[thread overview]
Message-ID: <20140404143413.GC17594@fieldses.org> (raw)
In-Reply-To: <20140404091324.699d0ba6@notabene.brown>

On Fri, Apr 04, 2014 at 09:13:24AM +1100, NeilBrown wrote:
> On Thu, 3 Apr 2014 17:36:10 -0400 "J. Bruce Fields" <bfields@fieldses.org>
> wrote:
> 
> > (BTW:  I also noticed the other day that systemd is calling
> > name_to_handle_at to get a mount id.  Seems like overkill in both
> > cases--shouldn't there be a simpler way to get just the mount id?)
> 
> Yes, it is called "xstat" and is an extensible version of stat which even
> includes a 'query' bitmap to list which things you want.

Yes.

I forget that encoding the filehandle is typically just reading inode
and generation number and encoding the results in a funny way, so it's
not particularly heavy-weight.

But lumping the two together does mean that your request can fail just
because the filesystem doesn't support nfs exports.

> Unfortunately it never made it to mainline.  We should submit a patch to
> systemd to get it to use xstat instead of name_to_handle_at.  That would
> ensure that the kernel implemented it double-quick :-)

Hm....

--b.

      reply	other threads:[~2014-04-04 14:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  5:46 Should exportfs/mountd cope with case-insensitive directory names NeilBrown
2014-04-03 13:09 ` J. Bruce Fields
2014-04-03 16:02   ` Boaz Harrosh
2014-04-03 17:16     ` J. Bruce Fields
2014-04-03 17:24       ` J. Bruce Fields
2014-04-03 21:21         ` NeilBrown
2014-04-03 21:36           ` J. Bruce Fields
2014-04-03 22:13             ` NeilBrown
2014-04-04 14:34               ` J. Bruce Fields [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=20140404143413.GC17594@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=openosd@gmail.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;
as well as URLs for NNTP newsgroup(s).