nfsd4: send the special close_stateid in v4.0 replies as well
authorJeff Layton <jlayton@redhat.com>
Thu, 15 Feb 2018 20:16:18 +0000 (15:16 -0500)
committerJ. Bruce Fields <bfields@redhat.com>
Mon, 19 Mar 2018 20:38:12 +0000 (16:38 -0400)
commitbd2decac5e8ab7b326f54b40e3ac8b3b1ac935ed
treeda654fb589e3c0ae0c48c479b89f886754730092
parent3b68e6ee3cbd4a474bcc7d2ac26812f86cdf333d
nfsd4: send the special close_stateid in v4.0 replies as well

We already send it for v4.1, but RFC7530 also notes that the stateid in
the close reply is bogus.

Always send the special close stateid, even in v4.0 responses. No client
should put any meaning on it whatsoever. For now, we continue to
increment the stateid value, though that might not be necessary either.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c