From: Trond Myklebust <trondmy@hammerspace.com>
To: "anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fs/nfs: Fix nfs_parse_devname to not modify it's argument
Date: Thu, 21 Feb 2019 22:41:59 +0000 [thread overview]
Message-ID: <0625ae525b9a9aa77c40b697fb39563163ee6d01.camel@hammerspace.com> (raw)
In-Reply-To: <87fttap7qp.fsf@xmission.com>
On Wed, 2019-01-30 at 07:58 -0600, Eric W. Biederman wrote:
> In the rare and unsupported case of a hostname list nfs_parse_devname
> will modify dev_name. There is no need to modify dev_name as the all
> that is being computed is the length of the hostname, so the computed
> length can just be shorted.
>
> Fixes: dc04589827f7 ("NFS: Use common device name parsing logic for
> NFSv4 and NFSv2/v3")
> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Thanks Eric! Applied to my linux-next branch for inclusion in the 5.1
merge window.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2019-02-21 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 13:58 [PATCH] fs/nfs: Fix nfs_parse_devname to not modify it's argument Eric W. Biederman
2019-02-21 22:41 ` Trond Myklebust [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=0625ae525b9a9aa77c40b697fb39563163ee6d01.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna.schumaker@netapp.com \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--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).