Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:36578 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751585AbbFZMRa (ORCPT ); Fri, 26 Jun 2015 08:17:30 -0400 Date: Fri, 26 Jun 2015 08:17:30 -0400 (EDT) From: Benjamin Coddington To: Trond Myklebust cc: Anders Blomdell , Linux NFS Mailing List Subject: Re: Mount regression between 4.0.4 client and 2.6.35 server In-Reply-To: Message-ID: References: <55827B8D.3070103@control.lth.se> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, 18 Jun 2015, Trond Myklebust wrote: > On Thu, Jun 18, 2015 at 4:04 AM, Anders Blomdell > 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