All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Fred Isaman <iisaman@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] pnfs-submit: prevent bad CB_LAYOUTRECALL from crashing client
Date: Wed, 17 Nov 2010 19:27:34 +0200	[thread overview]
Message-ID: <4CE41086.1030603@panasas.com> (raw)
In-Reply-To: <1289852433-18323-1-git-send-email-iisaman@netapp.com>

Thanks! Merged in pnfs-all-2.6.37-rc2-2010-11-17

Benny

On 2010-11-15 22:20, Fred Isaman wrote:
> An incorrect recall type sent by the server should result in
> the client returning BADXDR, not crashing the client.
> 
> Signed-off-by: Fred Isaman <iisaman@netapp.com>
> ---
>  fs/nfs/callback_proc.c |    3 +++
>  fs/nfs/callback_xdr.c  |    5 ++++-
>  2 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/nfs/callback_proc.c b/fs/nfs/callback_proc.c
> index b4c68e9..2274b6f 100644
> --- a/fs/nfs/callback_proc.c
> +++ b/fs/nfs/callback_proc.c
> @@ -139,6 +139,9 @@ _recall_matches_lget(struct pnfs_cb_lrecall_info *cb_info,
>  		return (ino == cb_info->pcl_ino) &&
>  			should_free_lseg(range, &cb_args->cbl_range);
>  	default:
> +		/* Should never hit here, as decode_layoutrecall_args()
> +		 * will verify cb_info from server.
> +		 */
>  		BUG();
>  	}
>  }
> diff --git a/fs/nfs/callback_xdr.c b/fs/nfs/callback_xdr.c
> index a77877c..2e1a33b 100644
> --- a/fs/nfs/callback_xdr.c
> +++ b/fs/nfs/callback_xdr.c
> @@ -246,7 +246,7 @@ static __be32 decode_layoutrecall_args(struct svc_rqst *rqstp,
>  	args->cbl_layoutchanged = ntohl(*p++);
>  	args->cbl_recall_type = ntohl(*p++);
>  
> -	if (likely(args->cbl_recall_type == RETURN_FILE)) {
> +	if (args->cbl_recall_type == RETURN_FILE) {
>  		args->cbl_range.iomode = iomode;
>  		status = decode_fh(xdr, &args->cbl_fh);
>  		if (unlikely(status != 0))
> @@ -270,6 +270,9 @@ static __be32 decode_layoutrecall_args(struct svc_rqst *rqstp,
>  		}
>  		p = xdr_decode_hyper(p, &args->cbl_fsid.major);
>  		p = xdr_decode_hyper(p, &args->cbl_fsid.minor);
> +	} else if (args->cbl_recall_type != RETURN_ALL) {
> +		status = htonl(NFS4ERR_BADXDR);
> +		goto out;
>  	}
>  	dprintk("%s: ltype 0x%x iomode %d changed %d recall_type %d\n",
>  		__func__,

      reply	other threads:[~2010-11-17 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 20:20 [PATCH 1/1] pnfs-submit: prevent bad CB_LAYOUTRECALL from crashing client Fred Isaman
2010-11-17 17:27 ` Benny Halevy [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=4CE41086.1030603@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=iisaman@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 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.