diff options
| author | Trond Myklebust <trond.myklebust@hammerspace.com> | 2024-02-24 23:59:28 +0300 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@hammerspace.com> | 2024-03-09 17:14:51 +0300 |
| commit | 0460253913e50a2aec911fe83090d60397f17664 (patch) | |
| tree | 516ae74bb5674b684efd4968a28635da1462bf65 /fs/remap_range.c | |
| parent | 2fdbc20036acda9e5694db74a032d3c605323005 (diff) | |
| download | linux-0460253913e50a2aec911fe83090d60397f17664.tar.xz | |
NFSv4: nfs4_do_open() is incorrectly triggering state recovery
We're seeing spurious calls to nfs4_schedule_stateid_recovery() from
nfs4_do_open() in situations where there is no trigger coming from the
server.
In theory the code path being triggered is supposed to notice that state
recovery happened while we were processing the open call result from the
server, before the open stateid is published. However in the years since
that code was added, we've also added the 'session draining' mechanism,
which ensures that the state recovery will wait until all the session
slots have been returned. In nfs4_do_open() the session slot is only
returned on exit of the function, so we don't need the legacy mechanism.
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'fs/remap_range.c')
0 files changed, 0 insertions, 0 deletions