| commit | bd3d16a887b0c19a2a20d35ffed499e3a3637feb | [log] [tgz] |
|---|---|---|
| author | Trond Myklebust <trond.myklebust@hammerspace.com> | Thu Jul 12 14:19:03 2018 -0400 |
| committer | Trond Myklebust <trond.myklebust@hammerspace.com> | Thu Jul 26 16:25:25 2018 -0400 |
| tree | 1c2ddddad9980c0668f902b3d2f9cee7c048455d | |
| parent | af9b6d7570ca9afbbc6076ab7920d8f00f7e55c1 [diff] |
NFSv4.1: Fix a potential layoutget/layoutrecall deadlock If the client is sending a layoutget, but the server issues a callback to recall what it thinks may be an outstanding layout, then we may find an uninitialised layout attached to the inode due to the layoutget. In that case, it is appropriate to return NFS4ERR_NOMATCHING_LAYOUT rather than NFS4ERR_DELAY, as the latter can end up deadlocking. Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>