On Tue, 2017-11-07 at 18:03 -0500, Andrew W Elble wrote:
> Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> writes:
>
> > On Tue, 2017-11-07 at 18:35 +0000, Trond Myklebust wrote:
> > >
> > > Ah, I see. Can we in that case please rather do the following?
> > >
> > >
> >
> > ...and then follow up with:
> >
> > 8<--------------------------------------------------------------
> > From 545e2fddb72268f5c59a3986169af96a40a6aab0 Mon Sep 17 00:00:00
> > 2001
> > From: Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx>
> > Date: Tue, 7 Nov 2017 12:39:44 -0500
> > Subject: [PATCH 2/2] NFSv4: Replace closed stateids with the
> > "invalid special
> > stateid"
> >
> > When decoding a CLOSE, replace the stateid returned by the server
> > with the "invalid special stateid" described in RFC5661, Section
> > 8.2.3.
> >
> > In nfs_set_open_stateid_locked, ignore stateids from closed state.
> >
> > Signed-off-by: Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx>
>
> Looks good! Thanks!
Thank you for testing! It has been very helpful...
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@xxxxxxxxxxxxxxx
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
