From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: "rydberg@euromail.se" <rydberg@euromail.se>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andre Heider <a.heider@gmail.com>
Subject: Re: Linux 3.11-rc2
Date: Tue, 23 Jul 2013 18:31:46 +0000 [thread overview]
Message-ID: <1374604305.12943.3.camel@leira.trondhjem.org> (raw)
In-Reply-To: <1374542261.7972.66.camel@leira.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
On Mon, 2013-07-22 at 21:17 -0400, Trond Myklebust wrote:
> On Tue, 2013-07-23 at 03:04 +0200, rydberg@euromail.se wrote:
> > Hi Trond, Linus,
> >
> > On Sun, Jul 21, 2013 at 12:53:10PM -0700, Linus Torvalds wrote:
> > > So it's been another week, and -rc2 is out there.
> >
> > This one happens to break nfs in a rather blunt-instrument fashion -
> > creating files on a nfs4 partition [1] no longer works. Bisection
> > yields this commit as the culprit:
> >
> > commit b4a2cf76ab7c08628c62b2062dacefa496b59dfd
> > Author: Trond Myklebust <Trond.Myklebust@netapp.com>
> > Date: Wed Jul 17 16:43:16 2013 -0400
> >
> > NFSv4: Fix a regression against the FreeBSD server
> >
> > Technically, the Linux client is allowed by the NFSv4 spec to send
> > 3 word bitmaps as part of an OPEN request. However, this causes the
> > current FreeBSD server to return NFS4ERR_ATTRNOTSUPP errors.
> >
> > Fix the regression by making the Linux client use a 2 word bitmap unless
> > doing NFSv4.2 with labeled NFS.
> >
> > Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
> >
> > Reverting the patch returns things to normal.
>
> - Can you please provide me with a binary tcpdump or wireshark dump that
> demonstrates the problem?
>
> - What server is this?
OK. With Andre's help, I think we've root caused the problem. Can you
please confirm that the attached patch also solves the issue for you?
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-NFSv4-Fix-brainfart-in-attribute-length-calculation.patch --]
[-- Type: text/x-patch; name="0001-NFSv4-Fix-brainfart-in-attribute-length-calculation.patch", Size: 1009 bytes --]
From 1f84e4f9ef9fc4ff502c112df049dfa6f656f4e0 Mon Sep 17 00:00:00 2001
From: Trond Myklebust <Trond.Myklebust@netapp.com>
Date: Tue, 23 Jul 2013 12:53:39 -0400
Subject: [PATCH] NFSv4: Fix brainfart in attribute length calculation
The calculation of the attribute length was 4 bytes off.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Tested-by: Andre Heider <a.heider@gmail.com>
---
fs/nfs/nfs4xdr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfs/nfs4xdr.c b/fs/nfs/nfs4xdr.c
index c74d616..3850b01 100644
--- a/fs/nfs/nfs4xdr.c
+++ b/fs/nfs/nfs4xdr.c
@@ -1118,11 +1118,11 @@ 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);
*q++ = htonl(bmval0);
*q++ = htonl(bmval1);
if (bmval_len == 3)
*q++ = htonl(bmval2);
+ len = (char *)p - (char *)(q + 1);
*q = htonl(len);
/* out: */
--
1.8.3.1
next prev parent reply other threads:[~2013-07-23 18:31 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 19:53 Linus Torvalds
2013-07-21 21:07 ` Tobias Klausmann
2013-07-22 13:08 ` Rafael J. Wysocki
2013-07-22 15:43 ` Tobias Klausmann
2013-07-21 23:08 ` James Hogan
2013-07-22 13:02 ` Rafael J. Wysocki
2013-07-22 13:15 ` Martin Steigerwald
2013-07-22 13:37 ` Rafael J. Wysocki
2013-07-22 18:46 ` Martin Steigerwald
2013-07-22 19:57 ` Rafael J. Wysocki
2013-07-24 5:10 ` Kalle Valo
2013-07-22 13:21 ` James Hogan
2013-07-22 18:11 ` Linus Torvalds
2013-07-22 19:54 ` Rafael J. Wysocki
2013-07-23 18:46 ` Linux 3.11-rc2 (acpi backlight) Kamal Mostafa
2013-07-24 0:05 ` Rafael J. Wysocki
2013-07-24 4:54 ` Steven Newbury
2013-07-24 6:49 ` James Hogan
2013-07-24 7:14 ` Mike Galbraith
2013-07-24 7:19 ` Igor Gnatenko
2013-07-24 12:06 ` Rafael J. Wysocki
2013-07-24 11:45 ` Jörg Otte
2013-07-25 13:00 ` Linux 3.11-rc2 (acpi backlight, revert) Rafael J. Wysocki
2013-07-25 14:43 ` Kamal Mostafa
2013-07-25 14:46 ` Daniel Vetter
2013-07-25 14:59 ` Kamal Mostafa
2013-07-25 14:52 ` Jörg Otte
2013-07-25 15:52 ` Jörg Otte
2013-07-25 19:14 ` James Hogan
2013-07-25 19:47 ` Rafael J. Wysocki
2013-07-26 4:23 ` Joerg Platte
2013-07-26 11:22 ` Igor Gnatenko
2013-07-26 7:43 ` Steven Newbury
2013-07-26 12:09 ` Martin Steigerwald
2013-07-26 12:40 ` Rafael J. Wysocki
2013-08-04 19:33 ` Martin Steigerwald
2013-08-04 22:15 ` Rafael J. Wysocki
2013-07-27 5:34 ` Kalle Valo
2013-07-27 12:18 ` Rafael J. Wysocki
2013-07-22 18:16 ` Linux 3.11-rc2 Matthew Garrett
2013-07-22 19:56 ` Rafael J. Wysocki
2013-07-23 17:47 ` Steven Newbury
2013-07-23 19:51 ` Matthew Garrett
2013-07-23 21:10 ` Steven Newbury
2013-07-23 21:24 ` Rafael J. Wysocki
2013-07-23 22:49 ` Steven Newbury
2013-07-22 1:25 ` Dave Chinner
2013-07-22 4:06 ` Al Viro
2013-07-24 3:22 ` Dave Chinner
2013-07-23 1:04 ` rydberg
2013-07-23 1:17 ` Myklebust, Trond
2013-07-23 18:31 ` Myklebust, Trond [this message]
2013-07-23 19:08 ` rydberg
2013-07-23 20:42 ` Linus Torvalds
2013-07-23 20:52 ` Myklebust, Trond
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=1374604305.12943.3.camel@leira.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=a.heider@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®