linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFSv4: Fix attribute length
Date: Wed, 24 Jul 2013 10:38:07 -0400	[thread overview]
Message-ID: <20130724143807.GI23378@fieldses.org> (raw)
In-Reply-To: <1374676257.12943.41.camel@leira.trondhjem.org>

On Wed, Jul 24, 2013 at 02:30:58PM +0000, Myklebust, Trond wrote:
> On Wed, 2013-07-24 at 10:14 -0400, J. Bruce Fields wrote:
> > From: "J. Bruce Fields" <bfields@redhat.com>
> > 
> > The calculation of attribute length fields is too high by four because
> > it incorrectly includes the length field itself.
> > 
> > This regression was introduced by
> > b4a2cf76ab7c08628c62b2062dacefa496b59dfd "NFSv4: Fix a regression
> > against the FreeBSD server" and causes OPENs to the Linux NFS server to
> > fail with BADXDR errors (translated by the client into EIO).
> > 
> > Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> > ---
> >  fs/nfs/nfs4xdr.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > I thought you guys had automated testing against the Linux server?  How
> > did this slip through into upstream?
> > 
> > --b.
> > 
> > diff --git a/fs/nfs/nfs4xdr.c b/fs/nfs/nfs4xdr.c
> > index c74d616..d6d6754 100644
> > --- a/fs/nfs/nfs4xdr.c
> > +++ b/fs/nfs/nfs4xdr.c
> > @@ -1118,7 +1118,7 @@ static void encode_attrs(struct xdr_stream *xdr, const struct iattr *iap,
> >  				len, ((char *)p - (char *)q) + 4);
> >  		BUG();
> >  	}
> > -	len = (char *)p - (char *)q - (bmval_len << 2);
> > +	len = (char *)p - (char *)q - (bmval_len + 1 << 2);
> >  	*q++ = htonl(bmval0);
> >  	*q++ = htonl(bmval1);
> >  	if (bmval_len == 3)
> 
> Please see commit 4f3cc4809a98a165a9708b72b47de71643797bbd (NFSv4: Fix
> brainfart in attribute length calculation) upstream.

Oh, good, thanks!

But I still don't understand how this made it into upstream in the first
place.

Any NFSv4 testing at all against the Linux server would catch this, and
I thought you had automated testing set up that you could run before
submission.

--b.

  reply	other threads:[~2013-07-24 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 14:14 [PATCH] NFSv4: Fix attribute length J. Bruce Fields
2013-07-24 14:30 ` Myklebust, Trond
2013-07-24 14:38   ` J. Bruce Fields [this message]
2013-07-24 14:41     ` Myklebust, Trond
2013-07-24 14:44       ` 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=20130724143807.GI23378@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@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 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).