From: Benny Halevy <bhalevy@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, eanderle@umich.edu
Subject: Re: [PATCH] pnfsd: Add IP address validation to nfsd4_set_pnfs_dlm_device()
Date: Mon, 14 Jun 2010 16:09:16 -0400 [thread overview]
Message-ID: <4C168C6C.5060508@panasas.com> (raw)
In-Reply-To: <20100614200001.GJ2745@fieldses.org>
On 2010-06-14 16:00, J. Bruce Fields wrote:
> From: Eric Anderle <eanderle@umich.edu>
>
> We should catch errors in the format at the time the list is given to
> the kernel, rather than just returning garbage to the client and letting
> the client fail.
>
> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> ---
> fs/nfsd/nfs4pnfsdlm.c | 29 +++++++++++++++++++++++------
> 1 files changed, 23 insertions(+), 6 deletions(-)
>
> diff --git a/fs/nfsd/nfs4pnfsdlm.c b/fs/nfsd/nfs4pnfsdlm.c
> index 1cf1b69..b6d9f23 100644
> --- a/fs/nfsd/nfs4pnfsdlm.c
> +++ b/fs/nfsd/nfs4pnfsdlm.c
> @@ -26,6 +26,7 @@
> #include <linux/nfsd/debug.h>
> #include <linux/nfsd/nfs4pnfsdlm.h>
> #include <linux/nfsd/nfs4layoutxdr.h>
> +#include <linux/sunrpc/clnt.h>
>
> #include "nfsfh.h"
> #include "nfsd.h"
> @@ -87,6 +88,24 @@ out:
> return ret;
> }
>
> +bool nfsd4_validate_pnfs_dlm_device(char *ds_list, int len, int *num_ds)
Is "len" used?
Benny
> +{
> + char *start = ds_list;
> +
> + *num_ds = 0;
> +
> + while (*start) {
> + struct sockaddr_storage tempAddr;
> + int ipLen = strcspn(start, ",");
> +
> + if (!rpc_pton(start, ipLen, (struct sockaddr *)&tempAddr, sizeof(tempAddr)))
> + return false;
> + (*num_ds)++;
> + start += ipLen + 1;
> + }
> + return true;
> +}
> +
> /*
> * pnfs_dlm_device string format:
> * block-device-path:<ds1 ipv4 address>,<ds2 ipv4 address>
> @@ -140,12 +159,10 @@ nfsd4_set_pnfs_dlm_device(char *pnfs_dlm_device, int len)
> goto out_free;
> memcpy(new->ds_list, bufp, len);
>
> - /* count the number of comma-delimited DS IPs */
> - new->num_ds = 1;
> - while ((bufp = strchr(bufp, ',')) != NULL) {
> - new->num_ds++;
> - bufp++;
> - }
> +
> + /* validate the ips */
> + if (!nfsd4_validate_pnfs_dlm_device(new->ds_list, len, &(new->num_ds)))
> + goto out_free;
>
> dprintk("%s disk_name %s num_ds %d ds_list %s\n", __func__,
> new->disk_name, new->num_ds, new->ds_list);
next prev parent reply other threads:[~2010-06-14 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 20:00 [PATCH] pnfsd: Add IP address validation to nfsd4_set_pnfs_dlm_device() J. Bruce Fields
2010-06-14 20:09 ` Benny Halevy [this message]
2010-06-15 0:09 ` Benny Halevy
2010-06-15 14:55 ` 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=4C168C6C.5060508@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@fieldses.org \
--cc=eanderle@umich.edu \
--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