From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Michael Groshans <groshans@citi.umich.edu>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SQUASHME: nfsd4: fix cb_recall encoding
Date: Tue, 25 May 2010 14:49:01 -0400 [thread overview]
Message-ID: <20100525184900.GD7085@fieldses.org> (raw)
In-Reply-To: <4BFB6AAA.5090308@panasas.com>
On Tue, May 25, 2010 at 09:14:02AM +0300, Benny Halevy wrote:
> On May. 24, 2010, 18:28 +0300, "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > From: J. Bruce Fields <bfields@citi.umich.edu>
> >
> > "nfsd: nfs4callback encode_stateid helper function" forgot to reserve
> > more space after return from the new helper.
> >
> > Reported-by: Michael Groshans <groshans@citi.umich.edu>
> > Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> > ---
> > fs/nfsd/nfs4callback.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > Benny, maybe you could fix that patch and then pass it upstream?
>
> Sure. I submitted this fix to the pnfs tree and will test and
> send a fixed version of "nfsd: nfs4callback encode_stateid helper function"
> upstream.
That's what I meant to say, yes, thanks!
--b.
>
> Benny
>
> >
> > --b.
> >
> > diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
> > index b279738..238e0b8 100644
> > --- a/fs/nfsd/nfs4callback.c
> > +++ b/fs/nfsd/nfs4callback.c
> > @@ -246,6 +246,7 @@ encode_cb_recall(struct xdr_stream *xdr, struct nfs4_delegation *dp,
> > RESERVE_SPACE(4);
> > WRITE32(OP_CB_RECALL);
> > encode_stateid(xdr, &dp->dl_stateid);
> > + RESERVE_SPACE(8 + (XDR_QUADLEN(len) << 2));
> > WRITE32(0); /* truncate optimization not implemented */
> > WRITE32(len);
> > WRITEMEM(&dp->dl_fh.fh_base, len);
>
prev parent reply other threads:[~2010-05-25 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:28 [PATCH] SQUASHME: nfsd4: fix cb_recall encoding J. Bruce Fields
2010-05-25 6:14 ` Benny Halevy
2010-05-25 18:49 ` J. Bruce Fields [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=20100525184900.GD7085@fieldses.org \
--to=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=groshans@citi.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;
as well as URLs for NNTP newsgroup(s).