From: Jim Rees <rees@umich.edu>
To: bjschuma@netapp.com
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] NFSD: Pass correct buffer size to rpc_ntop
Date: Fri, 7 Dec 2012 18:44:20 -0500 [thread overview]
Message-ID: <20121207234420.GA11001@umich.edu> (raw)
In-Reply-To: <1354915049-6892-1-git-send-email-bjschuma@netapp.com>
bjschuma@netapp.com wrote:
From: Bryan Schumaker <bjschuma@netapp.com>
I honestly have no idea where I got 129 from, but it's a much bigger
value than the actual buffer size (INET6_ADDRSTRLEN).
128 for the number of bits in an ip6 address, plus one more for the null
terminator bit?
(yes, I'm joking, for those of you with no sense of humor)
next prev parent reply other threads:[~2012-12-07 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 21:17 [PATCH 1/2] NFSD: Pass correct buffer size to rpc_ntop bjschuma
2012-12-07 21:17 ` [PATCH 2/2] NFSD: Correct the size calculation in fault_inject_write bjschuma
2012-12-07 23:44 ` Jim Rees [this message]
2012-12-10 23:08 ` [PATCH 1/2] NFSD: Pass correct buffer size to rpc_ntop J. Bruce Fields
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=20121207234420.GA11001@umich.edu \
--to=rees@umich.edu \
--cc=bfields@fieldses.org \
--cc=bjschuma@netapp.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 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).