From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: <Trond.Myklebust@primarydata.com>, <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2] NFS: Add stubs for GETDEVICELIST
Date: Tue, 14 Apr 2015 10:34:46 -0400 [thread overview]
Message-ID: <552D2586.902@Netapp.com> (raw)
In-Reply-To: <20150413174538.GA22583@infradead.org>
On 04/13/2015 01:45 PM, Christoph Hellwig wrote:
> On Fri, Apr 10, 2015 at 11:42:39AM -0400, Anna Schumaker wrote:
>> d4b18c3e (pnfs: remove GETDEVICELIST implementation) removed the
>> GETDEVICELIST operation from the NFS client, but left a "hole" in the
>> nfs4_procedures array. This caused /proc/self/mountstats to report an
>> operation named "51" where GETDEVICELIST used to be. This patch adds
>> back stubs to fix mountstats.
>
> The only thing we need here is the name, right? Why not add a STUB
> macro that just fills out the name field?
Good idea. I just sent a patch to do just that!
Anna
>
prev parent reply other threads:[~2015-04-14 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 15:42 [PATCH v2] NFS: Add stubs for GETDEVICELIST Anna Schumaker
2015-04-13 17:45 ` Christoph Hellwig
2015-04-14 14:34 ` Anna Schumaker [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=552D2586.902@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=Trond.Myklebust@primarydata.com \
--cc=hch@infradead.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 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.