From: "J. Bruce Fields" <bfields@fieldses.org>
To: Boaz Harrosh <openosd@gmail.com>
Cc: NeilBrown <neilb@suse.de>, NFS <linux-nfs@vger.kernel.org>
Subject: Re: Should exportfs/mountd cope with case-insensitive directory names.
Date: Thu, 3 Apr 2014 13:24:31 -0400 [thread overview]
Message-ID: <20140403172431.GB5884@fieldses.org> (raw)
In-Reply-To: <20140403171625.GA5884@fieldses.org>
On Thu, Apr 03, 2014 at 01:16:25PM -0400, J. Bruce Fields wrote:
> In the presence of bind mounts it's definitely possible for two
> different paths to reach the same directory.
>
> I don't know if that's actually a problem here....
Without testing: if we've got the same filesystem mounted at /foo/bar
and /foo/baz, but only export /foo/bar, will this change make that
export show up at /foo/baz as well?
(Since we'll now consider /foo/bar and /foo/baz to match where
previously they didn't?)
--b.
next prev parent reply other threads:[~2014-04-03 17:24 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 [this message]
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
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=20140403172431.GB5884@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).