From: Malahal Naineni <malahal@us.ibm.com>
To: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Check for beginning '/' in the mount path
Date: Mon, 6 Feb 2012 12:11:02 -0600 [thread overview]
Message-ID: <20120206181102.GA9086@us.ibm.com> (raw)
In-Reply-To: <4F2E620F.5090100@panasas.com>
Boaz Harrosh [bharrosh@panasas.com] wrote:
> I think that both fixes to umount are important for future/backward
> compatibility with Kernel, And general code resilience.
>
> But some kind sole should fix both breakages in /proc/mounts, for
> sure. Would you know how to fix it?
I guess, fixing the umount is needed and it is easy. I will send a fix.
The kernel side is not as easy! The NFS4 mounts the root first then the
exported path using subtree_mount() which seem to remove the actual
string and replace it with a real path. We can save the devname
somewhere and get it into nfs_show_devname(), but I am not sure that
works.
Thanks, Malahal.
next prev parent reply other threads:[~2012-02-06 18:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 1:42 [PATCH] Check for beginning '/' in the mount path Malahal Naineni
2012-02-03 11:15 ` Boaz Harrosh
2012-02-03 12:16 ` NeilBrown
2012-02-03 14:29 ` Malahal Naineni
2012-02-05 11:03 ` Boaz Harrosh
2012-02-06 18:11 ` Malahal Naineni [this message]
2012-02-07 20:44 ` [PATCH] Get normalized paths for comparing NFS export paths Malahal Naineni
2012-02-16 18:09 ` Malahal Naineni
2012-03-02 19:10 ` Steve Dickson
2012-03-02 19:27 ` Malahal Naineni
2012-03-02 20:57 ` Steve Dickson
2012-03-02 22:01 ` Malahal Naineni
2012-03-03 17:39 ` Steve Dickson
2012-03-03 19:12 ` Myklebust, Trond
2012-03-04 22:31 ` Steve Dickson
2012-03-04 22:46 ` Myklebust, Trond
2012-03-04 23:08 ` Steve Dickson
2012-03-05 4:46 ` Malahal Naineni
2012-03-05 12:03 ` Steve Dickson
2012-03-04 22:58 ` Steve Dickson
2012-03-04 23:26 ` Myklebust, Trond
2012-03-05 0:03 ` Steve Dickson
2012-03-05 2:04 ` Myklebust, Trond
2012-03-05 4:53 ` Malahal Naineni
2012-03-05 11:55 ` Steve Dickson
2012-03-05 14:47 ` Malahal Naineni
2012-03-05 15:03 ` Steve Dickson
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=20120206181102.GA9086@us.ibm.com \
--to=malahal@us.ibm.com \
--cc=linux-nfs@vger.kernel.org \
/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).