From: Ben Hutchings <ben@decadent.org.uk>
To: Xiong Zhou <xzhou@redhat.com>
Cc: trond.myklebust@primarydata.com, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfs: use canonical path in nfs_show_devname
Date: Wed, 20 Aug 2014 16:10:35 -0700 [thread overview]
Message-ID: <1408576235.2618.47.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <1927160445.21851828.1408504000719.JavaMail.zimbra@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Tue, 2014-08-19 at 23:06 -0400, Xiong Zhou wrote:
> When export root dir(/) via nfs, and mount a particular dir under root, eg
> /nfsexport, there will be defect double slash output in /proc/mounts, like
> localhost://nfsexport.
>
> Signed-off-by: Xiong Zhou <xzhou@redhat.com>
> ---
> fs/nfs/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> index e4499d5..62b1cab 100644
> --- a/fs/nfs/super.c
> +++ b/fs/nfs/super.c
> @@ -780,7 +780,7 @@ int nfs_show_devname(struct seq_file *m, struct dentry *root)
> int err = 0;
> if (!page)
> return -ENOMEM;
> - devname = nfs_path(&dummy, root, page, PAGE_SIZE, 0);
> + devname = nfs_path(&dummy, root, page, PAGE_SIZE, 1);
> if (IS_ERR(devname))
> err = PTR_ERR(devname);
> else
This will reintroduce the problem reported in
<https://bugs.debian.org/669314>.
Ben.
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-08-20 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <600788954.21849581.1408502615727.JavaMail.zimbra@redhat.com>
2014-08-20 3:06 ` Xiong Zhou
2014-08-20 23:10 ` Ben Hutchings [this message]
2014-08-25 5:51 ` [PATCH v2] nfs: remove redundant slash from nfs_path Xiong Zhou
2014-08-25 21:07 ` Ben Hutchings
2014-08-25 21:17 ` Trond Myklebust
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=1408576235.2618.47.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=xzhou@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®