All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: fanchaoting <fanchaoting@cn.fujitsu.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH]spnfs-block: reserve space error in bl_encode_stripe
Date: Mon, 25 Mar 2013 11:40:15 +0200	[thread overview]
Message-ID: <51501B7F.6040506@tonian.com> (raw)
In-Reply-To: <513DC5BE.9000103@cn.fujitsu.com>

On 2013-03-11 13:53, fanchaoting wrote:
>  when useing spnfs-block, reserve space error in bl_encode_stripe.
> 
>  Signed-off-by: fanchaoting<fanchaoting@cn.fujitsu.com>

Good catch!
This patch did not apply cleanly on my latest pnfsd-block branch.
Please rebase onto the newest branch and send an up-to-date patch next time.

Merged into git://linux-nfs.org/~bhalevy/linux-pnfs.git pnfsd-block

Thanks,

Benny

> ---
>  fs/exportfs/nfs4blocklayoutxdr.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/exportfs/nfs4blocklayoutxdr.c b/fs/exportfs/nfs4blocklayoutxdr.c
> index 439e647..c942d34 100644
> --- a/fs/exportfs/nfs4blocklayoutxdr.c
> +++ b/fs/exportfs/nfs4blocklayoutxdr.c
> @@ -53,7 +53,7 @@ static int
>  bl_encode_stripe(struct exp_xdr_stream *xdr, pnfs_blocklayout_devinfo_t *bld)
>  {
>         int i;
> -       __be32 *p = exp_xdr_reserve_space(xdr,
> +       __be32 *p = exp_xdr_reserve_qwords(xdr,
>                                           2 + 1 + bld->u.stripe.bld_stripes);
> 
>         p = exp_xdr_encode_u64(p, bld->u.stripe.bld_chunk_size);
> --
> 1.7.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2013-03-25  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 11:53 [PATCH]spnfs-block: reserve space error in bl_encode_stripe fanchaoting
2013-03-25  9:40 ` 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=51501B7F.6040506@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=fanchaoting@cn.fujitsu.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.