diff options
| author | Jeff Layton <jlayton@redhat.com> | 2018-02-15 15:16:18 -0500 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2018-03-19 16:38:12 -0400 |
| commit | bd2decac5e8ab7b326f54b40e3ac8b3b1ac935ed (patch) | |
| tree | da654fb589e3c0ae0c48c479b89f886754730092 /fs/lockd | |
| parent | 3b68e6ee3cbd4a474bcc7d2ac26812f86cdf333d (diff) | |
| download | linux-bd2decac5e8ab7b326f54b40e3ac8b3b1ac935ed.tar.bz2 | |
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>
Diffstat (limited to 'fs/lockd')
0 files changed, 0 insertions, 0 deletions