All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org, Josh Boyer <jwboyer@redhat.com>
Subject: Re: [PATCH] nfs: Enclose hostname in brackets when needed in nfs_do_root_mount
Date: Tue, 8 Nov 2011 14:06:08 +0100	[thread overview]
Message-ID: <20111108130608.GA16554@quack.suse.cz> (raw)
In-Reply-To: <20110903002231.GI12182@quack.suse.cz>

On Sat 03-09-11 02:22:31, Jan Kara wrote:
> On Fri 02-09-11 16:23:43, Myklebust, Trond wrote:
> > > -----Original Message-----
> > > From: Jan Kara [mailto:jack@suse.cz]
> > > Sent: Friday, September 02, 2011 7:10 PM
> > > To: Myklebust, Trond
> > > Cc: linux-nfs@vger.kernel.org; Jan Kara; Josh Boyer; Myklebust, Trond
> > > Subject: [PATCH] nfs: Enclose hostname in brackets when needed in
> > > nfs_do_root_mount
> > > 
> > > When hostname contains colon (e.g. when it is an IPv6 address) it
> > needs
> > > to be enclosed in brackets to make parsing of NFS device string
> > > possible.
> > > Fix nfs_do_root_mount() to enclose hostname properly when needed. NFS
> > > code
> > > actually does not need this as it does not parse the string passed by
> > > nfs_do_root_mount() but the device string is exposed to userspace in
> > > /proc/mounts.
> > > 
> > > CC: Josh Boyer <jwboyer@redhat.com>
> > > CC: Trond Myklebust <Trond.Myklebust@netapp.com>
> > > Signed-off-by: Jan Kara <jack@suse.cz>
> > > ---
> > >  fs/nfs/super.c |    8 ++++++--
> > >  1 files changed, 6 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> > > index b961cea..42b74f8 100644
> > > --- a/fs/nfs/super.c
> > > +++ b/fs/nfs/super.c
> > > @@ -2694,11 +2694,15 @@ static struct vfsmount
> > > *nfs_do_root_mount(struct file_system_type *fs_type,
> > >  	char *root_devname;
> > >  	size_t len;
> > > 
> > > -	len = strlen(hostname) + 3;
> > > +	len = strlen(hostname) + 5;
> > >  	root_devname = kmalloc(len, GFP_KERNEL);
> > >  	if (root_devname == NULL)
> > >  		return ERR_PTR(-ENOMEM);
> > > -	snprintf(root_devname, len, "%s:/", hostname);
> > > +	/* Does hostname needs to be enclosed in brackets? */
> > > +	if (strchr(hostname, ':'))
> > > +		snprintf(root_devname, len, "[%s]:/", hostname);
> > > +	else
> > > +		snprintf(root_devname, len, "%s:/", hostname);
> > 
> > What if the hostname is already enclosed in brackets, as is usually the
> > case if I enter an IPv6 address instead of a DNS name? Won't this cause
> > it to be bracketed twice?
> > 
> > IOW: If I try to
> > 
> > 	mount -t nfs [fe80::20c:29ff:fee9:83e6]:/export /mnt
> > 
> > won't the above end up returning a hostname of [[::20c:29ff:fee9:83e6]]?
>   No it won't - I've actually verified my patch with experiment ;). The
> hostname nfs_do_root_mount() gets is already without possible brackets
> (these have been removed when we first parsed the string passed from
> userspace by nfs_parse_devname() - yes, it took me some time to drill
> through the NFS call stack during mount to actually find out who removes
> the brackets from the passed hostname and who composes the device name back
> without them).
  Ping? Trond, will you merge the patch please? I guess it got somehow
lost.

								Honza

  reply	other threads:[~2011-11-08 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-02 23:09 [PATCH] nfs: Enclose hostname in brackets when needed in nfs_do_root_mount Jan Kara
2011-09-02 23:23 ` Myklebust, Trond
2011-09-03  0:22   ` Jan Kara
2011-11-08 13:06     ` Jan Kara [this message]
2011-12-20 13:41       ` Josh Boyer

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=20111108130608.GA16554@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=Trond.Myklebust@netapp.com \
    --cc=jwboyer@redhat.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 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.