Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/4] NFS: Add string length argument to nfs_parse_server_address
Date: Thu, 19 Jun 2008 13:43:43 -0400	[thread overview]
Message-ID: <1213897423.7120.17.camel@localhost> (raw)
In-Reply-To: <20080618223211.16006.8247.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>

On Wed, 2008-06-18 at 18:32 -0400, Chuck Lever wrote:
> To make nfs_parse_server_address() more generally useful, allow it to
> accept input strings that are not terminated with '\0'.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> 
>  fs/nfs/super.c |  107 ++++++++++++++++++++++++++++++++++++++++----------------
>  1 files changed, 77 insertions(+), 30 deletions(-)
> 
> 
> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> index 98c8110..818bc1b 100644
> --- a/fs/nfs/super.c
> +++ b/fs/nfs/super.c
> @@ -62,6 +62,13 @@
>  
>  #define NFSDBG_FACILITY		NFSDBG_VFS
>  
> +#ifndef INET_ADDRSTRLEN
> +#define INET_ADDRSTRLEN		(16)
> +#endif
> +#ifndef INET6_ADDRSTRLEN
> +#define INET6_ADDRSTRLEN	(48)
> +#endif
> +

If you're resending, then can you please get rid of the above #ifndefs?
If somebody else is defining an INET_ADDRSTRLEN that overrides ours,
then I definitely want to know about it at compile time, so that I can
check for correctness.

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

  parent reply	other threads:[~2008-06-19 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 22:31 [PATCH 0/4] NFS mounting with raw IPv6 server hostnames (take 2) Chuck Lever
     [not found] ` <20080618222951.16006.3679.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-18 22:31   ` [PATCH 1/4] NFS: Use common device name parsing logic for NFSv4 and NFSv2/v3 Chuck Lever
2008-06-18 22:32   ` [PATCH 2/4] NFS: Support raw IPv6 address hostnames during NFS mount operation Chuck Lever
     [not found]     ` <20080618223203.16006.61765.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-18 22:35       ` Peter Staubach
2008-06-18 22:42         ` Chuck Lever
2008-06-18 22:51           ` Trond Myklebust
2008-06-18 22:59             ` Peter Staubach
2008-06-18 22:32   ` [PATCH 3/4] NFS: Add string length argument to nfs_parse_server_address Chuck Lever
     [not found]     ` <20080618223211.16006.8247.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-19 17:43       ` Trond Myklebust [this message]
2008-06-18 22:32   ` [PATCH 4/4] NFS: handle interface identifiers in incoming IPv6 addresses Chuck Lever
  -- strict thread matches above, loose matches on Subject: below --
2008-06-23 16:36 [PATCH 0/4] NFS mounting with raw IPv6 server hostnames (take 3) Chuck Lever
     [not found] ` <20080623163129.10539.15565.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-23 16:36   ` [PATCH 3/4] NFS: Add string length argument to nfs_parse_server_address Chuck Lever
2008-06-17 18:17 [PATCH 0/4] NFS mounting with raw IPv6 server hostnames Chuck Lever
     [not found] ` <20080617181622.3215.61295.stgit-ewv44WTpT0t9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2008-06-17 18:17   ` [PATCH 3/4] NFS: Add string length argument to nfs_parse_server_address Chuck Lever

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=1213897423.7120.17.camel@localhost \
    --to=trond.myklebust@netapp.com \
    --cc=chuck.lever@oracle.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