From owner-freebsd-fs@freebsd.org  Thu Jul  2 03:29:32 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79C909926C9
 for <freebsd-fs@mailman.ysv.freebsd.org>; Thu,  2 Jul 2015 03:29:32 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "vps1.elischer.org",
 Issuer "CA Cert Signing Authority" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 521432ABA
 for <freebsd-fs@freebsd.org>; Thu,  2 Jul 2015 03:29:32 +0000 (UTC)
 (envelope-from julian@freebsd.org)
Received: from Julian-MBP3.local (ppp121-45-238-82.lns20.per1.internode.on.net
 [121.45.238.82]) (authenticated bits=0)
 by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t623TJLr002737
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
 Wed, 1 Jul 2015 20:29:22 -0700 (PDT)
 (envelope-from julian@freebsd.org)
Message-ID: <5594B008.10202@freebsd.org>
Date: Thu, 02 Jul 2015 11:29:12 +0800
From: Julian Elischer <julian@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Rick Macklem <rmacklem@uoguelph.ca>, d@delphij.net
CC: freebsd-fs@freebsd.org
Subject: Re: Linux NFSv4 clients are getting (bad sequence-id error!)
References: <CANzjMX45QaC8yZx2nHPAohJRvQjmUOHuhMQWP9nX+srJs707Hg@mail.gmail.com>
 <684628776.2772174.1435793776748.JavaMail.zimbra@uoguelph.ca>
 <CANzjMX7xKBvnzJhQhB_ZrUnyE2m_FJXXy4fm_RFnuZfBDyDm2A@mail.gmail.com>
 <55947C6E.5060409@delphij.net>
 <1491630362.2785531.1435799383802.JavaMail.zimbra@uoguelph.ca>
In-Reply-To: <1491630362.2785531.1435799383802.JavaMail.zimbra@uoguelph.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2015 03:29:32 -0000

On 7/2/15 9:09 AM, Rick Macklem wrote:
> I am going to post to nfsv4@ietf.org to see what they say. Please 
> let me know if Xin Li's patch resolves your problem, even though I 
> don't believe it is correct except for the UINT32_MAX case. Good 
> luck with it, rick
and please keep us all in the loop as to what they say!

the general N+2 bit sounds like bullshit to me.. its always N+1 in a 
number field that has a
bit of slack at wrap time (probably due to some ambiguity in the 
original spec).