From: Benjamin Coddington <bcodding@redhat.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Anders Blomdell <anders.blomdell@control.lth.se>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Mount regression between 4.0.4 client and 2.6.35 server
Date: Fri, 26 Jun 2015 08:17:30 -0400 (EDT) [thread overview]
Message-ID: <alpine.OSX.2.19.9992.1506260807060.13917@planck.local> (raw)
In-Reply-To: <CAHQdGtS1affPWS=MLM8cn4C-JYjjbJUf2jHaK7uomLLkKc12HA@mail.gmail.com>
On Thu, 18 Jun 2015, Trond Myklebust wrote:
> On Thu, Jun 18, 2015 at 4:04 AM, Anders Blomdell
> <anders.blomdell@control.lth.se> wrote:
> >
> > I have a problem with a 4.0.4 client refusing to mount from a 2.6.35 server
> > due to NFS4ERR_INVAL returned during nfs4_discover_server_trunking. See
> > https://bugzilla.redhat.com/show_bug.cgi?id=1228272.
>
>
> Why should we change the clients if the server is in clear and obvious
> violation of the spec?
What's happening here is knfsd older than 2.6.38 will return NFS4ERR_INVAL
for EXCHANGE_ID that has EXCHGID4_FLAG_BIND_PRINC_STATEID set in the
request.
Should the client's use of stateid/princ binding be optional/configureable?
Ben
next prev parent reply other threads:[~2015-06-26 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 8:04 Mount regression between 4.0.4 client and 2.6.35 server Anders Blomdell
2015-06-18 11:49 ` Trond Myklebust
2015-06-18 12:28 ` Anders Blomdell
2015-06-18 12:53 ` Trond Myklebust
2015-06-18 14:20 ` Steve Dickson
2015-06-26 12:17 ` Benjamin Coddington [this message]
2015-06-26 17:50 ` J. Bruce Fields
2015-06-26 17:58 ` Trond Myklebust
2015-06-26 18:32 ` 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=alpine.OSX.2.19.9992.1506260807060.13917@planck.local \
--to=bcodding@redhat.com \
--cc=anders.blomdell@control.lth.se \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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.