diff options
| author | J. Bruce Fields <bfields@redhat.com> | 2014-05-20 15:55:21 -0400 |
|---|---|---|
| committer | Jiri Slaby <jslaby@suse.cz> | 2014-06-09 15:53:34 +0200 |
| commit | 94b7b52bd91e0bb9ed304d7f5de3711defdc42c6 (patch) | |
| tree | ed68843322f01535f0c70ba19128e25e36a12bcf /arch | |
| parent | a55dfea8623fadef4f0985be3f84a54a92718192 (diff) | |
nfsd4: remove lockowner when removing lock stateid
commit a1b8ff4c97b4375d21b6d6c45d75877303f61b3b upstream.
The nfsv4 state code has always assumed a one-to-one correspondance
between lock stateid's and lockowners even if it appears not to in some
places.
We may actually change that, but for now when FREE_STATEID releases a
lock stateid it also needs to release the parent lockowner.
Symptoms were a subsequent LOCK crashing in find_lockowner_str when it
calls same_lockowner_ino on a lockowner that unexpectedly has an empty
so_stateids list.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions