From owner-freebsd-fs@freebsd.org Thu Jul 2 21:41:20 2015 Return-Path: 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 3317E992559 for ; Thu, 2 Jul 2015 21:41:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id C5FC4112E; Thu, 2 Jul 2015 21:41:19 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2B7AwCzr5VV/61jaINbg2ZfBoMZuhgJgWQKhXgCggkUAQEBAQEBAYEKhCMBAQECAgEBASAERwsMBAIBCA4KAgINGQICJzACBBOILw22WpYgAQEBAQEFAQEBAQEBARcEgSGKKYQ7FwEzB4JogUMFhwiGMoZYhGGEYoNdFIcPj2oCJoQWIjEBgUaBBAEBAQ X-IronPort-AV: E=Sophos;i="5.15,395,1432612800"; d="scan'208";a="223544926" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-annu.net.uoguelph.ca with ESMTP; 02 Jul 2015 17:41:18 -0400 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 9EDC615F533; Thu, 2 Jul 2015 17:41:18 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 1XfrOzacyfLA; Thu, 2 Jul 2015 17:41:15 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 23C7C15F54D; Thu, 2 Jul 2015 17:41:15 -0400 (EDT) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id KcyImgs8proe; Thu, 2 Jul 2015 17:41:15 -0400 (EDT) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 06CC215F533; Thu, 2 Jul 2015 17:41:15 -0400 (EDT) Date: Thu, 2 Jul 2015 17:41:15 -0400 (EDT) From: Rick Macklem To: Ahmed Kamal Cc: Julian Elischer , Freebsd fs , d@delphij.net Message-ID: <1919954909.3441620.1435873275001.JavaMail.zimbra@uoguelph.ca> In-Reply-To: References: <1427974645.2786896.1435800121257.JavaMail.zimbra@uoguelph.ca> Subject: Re: [nfsv4] Is "skip by 1" allowed for the NFSv4.0 seqid? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF34 (Win)/8.0.9_GA_6191) Thread-Topic: Is "skip by 1" allowed for the NFSv4.0 seqid? Thread-Index: QLEgmE4pXFcQ2frzSVqAv4V1Er5qqg== X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jul 2015 21:41:20 -0000 Here is the response on nfsv4@ietf.org. I think the Redhat client is broken from reading this. It will be interesting to see if anyone working on the Linux client responds. rick ----- Original Message ----- > > Is "skip by 1" allowed for NFv4.0 seqid? >=20 > No it isn't. As you indicated RFC7530, which obsoletes RFC3530,, indicate= s > you are' > only allowed to increment by one, with the exception of the wraparound ca= se. >=20 > > I'll admit the wording in RFC-3530 isn't ideal, >=20 > I think the text "(r =3D=3D L+2)" is intended to be read as "(e.g. r =3D= =3D L+2)" but > the existing text > is unclear. >=20 > > but I've never heard of this interpretation before . >=20 > Me either. >=20 > > Is an NFSv4.0 server supposed to accept both 0 and 1 as the > correct next sequence # after UINT32_MAX? >=20 > I would say it isn't.=C2=A0 RFC7530 says "If th e sequence value received= is any > other > value, it is rejected with the return of error NFS4ERR_BAD_SEQID" In thi= s > case > the correct value is 1. On the other hand, this isn't a "MUST". If ther= e > are clients out > out there that don't do seqid wraparound correctly, it is seems like a > reasonable > accommodation for a server to accept the incorrect value zero in this cas= e., >=20 >=20 >=20 >=20 >=20 >=20 > On Wed, Jul 1, 2015 at 9:22 PM, Rick Macklem < rmacklem@uoguelph.ca > wro= te: >=20 >=20 > Hi, >=20 > If you look here (on page #6) it seems to indicate that > incrementing the seqid by 2 is allowed by the RFC. > (I'll admit the wording in RFC-3530 isn't ideal, but I've > never heard of this interpretation before.) > https://dl.dropboxusercontent.com/u/51939288/nfs4-bad-seq.pdf >=20 > RFC-7530 seems clear that it should only be incremented by 1. > However, I do notice that a wraparound of the seqid is supposed > to skip 0 and go to 1. I don't see any mention of this in RFC-3530. > --> Is an NFSv4.0 server supposed to accept both 0 and 1 as the > correct next sequence # after UINT32_MAX? >=20 > Thanks for any help clarifying this, rick >=20 > _______________________________________________ > nfsv4 mailing list > nfsv4@ietf.org > https://www.ietf.org/mailman/listinfo/nfsv4 >=20 >=20 > _______________________________________________ > nfsv4 mailing list > nfsv4@ietf.org > https://www.ietf.org/mailman/listinfo/nfsv4 >=20