From: Kinglong Mee <kinglongmee@gmail.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] nfs: Fix showing truncated fsid/dev in /proc/net/nfsfs/volumes
Date: Sat, 13 Jun 2015 08:58:42 +0800 [thread overview]
Message-ID: <557B8042.8010208@gmail.com> (raw)
In-Reply-To: <CAHQdGtSB9s6m12Y2pY+JYToLcak9Q-vw-ybC0-UbBPJQUd0P+A@mail.gmail.com>
On 6/12/2015 10:04 PM, Trond Myklebust wrote:
> On Fri, Jun 12, 2015 at 9:47 AM, Kinglong Mee <kinglongmee@gmail.com> wrote:
>> A truncated fsid showing from /proc/fs/nfsfs/volumes as,
>> # cat /proc/fs/nfsfs/volumes
>> NV SERVER PORT DEV FSID FSC
>> v4 c0a80881 801 0:43 34931f044c2a439b no
>>
>> It should be as,
>> # cat /proc/fs/nfsfs/volumes
>> NV SERVER PORT DEV FSID FSC
>> v4 c0a80881 801 0:43 34931f044c2a439b:954c5d830fa4be8c no
>>
>> The max buffer length for storing "%llx:%llx" format should be
>> 16 + 1 + 16 + 1 = 34 (16 for %llx, 1 for ':', 1 for '\0').
>>
>> Also, for storing "%u:%u" of MAJOR() and MINOR() should be
>> 8 + 1 + 3 + 1 = 13 (8 for 2^24, 1 for ':', 3 for 2^8, 1 for '\0').
Here is the comments for why buffer size is 13 and 34.
>>
>> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
>> ---
>> fs/nfs/client.c | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/fs/nfs/client.c b/fs/nfs/client.c
>> index 892aeff..873f194 100644
>> --- a/fs/nfs/client.c
>> +++ b/fs/nfs/client.c
>> @@ -1364,27 +1364,28 @@ static int nfs_volume_list_show(struct seq_file *m, void *v)
>> {
>> struct nfs_server *server;
>> struct nfs_client *clp;
>> - char dev[8], fsid[17];
>> + char dev[13], fsid[34];
>
> Could use a comment to explain why these particular sizes.
>
>> struct nfs_net *nn = net_generic(seq_file_net(m), nfs_net_id);
>>
>> /* display header on line 1 */
>> if (v == &nn->nfs_volume_list) {
>> - seq_puts(m, "NV SERVER PORT DEV FSID FSC\n");
>> + seq_puts(m, "NV SERVER PORT DEV FSID"
>> + " FSC\n");
>> return 0;
>> }
>> /* display one transport per line on subsequent lines */
>> server = list_entry(v, struct nfs_server, master_link);
>> clp = server->nfs_client;
>>
>> - snprintf(dev, 8, "%u:%u",
>> + snprintf(dev, 13, "%u:%u",
>
> Is there any reason not to settle for using sizeof(dev) here?
No, I just modify it as before.
I will update it as using sizeof(dev) in the new version.
thanks,
Kinglong Mee
>
>> MAJOR(server->s_dev), MINOR(server->s_dev));
>>
>> - snprintf(fsid, 17, "%llx:%llx",
>> + snprintf(fsid, 34, "%llx:%llx",
>
> ditto
>
>> (unsigned long long) server->fsid.major,
>> (unsigned long long) server->fsid.minor);
>>
>> rcu_read_lock();
>> - seq_printf(m, "v%u %s %s %-7s %-17s %s\n",
>> + seq_printf(m, "v%u %s %s %-12s %-33s %s\n",
>> clp->rpc_ops->version,
>> rpc_peeraddr2str(clp->cl_rpcclient, RPC_DISPLAY_HEX_ADDR),
>> rpc_peeraddr2str(clp->cl_rpcclient, RPC_DISPLAY_HEX_PORT),
>> --
>> 2.4.3
>>
>
next prev parent reply other threads:[~2015-06-13 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 13:47 [PATCH] nfs: Fix showing truncated fsid/dev in /proc/net/nfsfs/volumes Kinglong Mee
2015-06-12 14:04 ` Trond Myklebust
2015-06-13 0:58 ` Kinglong Mee [this message]
2015-06-13 2:07 ` [PATCH v2] nfs: Fix showing truncated fsid/dev in, /proc/net/nfsfs/volumes Kinglong Mee
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=557B8042.8010208@gmail.com \
--to=kinglongmee@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 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.