diff options
| author | Trond Myklebust <trond.myklebust@hammerspace.com> | 2024-12-16 19:28:06 -0500 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@hammerspace.com> | 2024-12-17 11:10:55 -0500 |
| commit | 62e2a47ceab8f3f7d2e3f0e03fdd1c5e0059fd8b (patch) | |
| tree | d2a927ec139307f460f34e28be78182a59fdd372 /tools/testing/selftests/net/lib/py/ynl.py | |
| parent | 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8 (diff) | |
| download | linux-62e2a47ceab8f3f7d2e3f0e03fdd1c5e0059fd8b.tar.gz linux-62e2a47ceab8f3f7d2e3f0e03fdd1c5e0059fd8b.tar.bz2 linux-62e2a47ceab8f3f7d2e3f0e03fdd1c5e0059fd8b.zip | |
NFS/pnfs: Fix a live lock between recalled layouts and layoutget
When the server is recalling a layout, we should ignore the count of
outstanding layoutget calls, since the server is expected to return
either NFS4ERR_RECALLCONFLICT or NFS4ERR_RETURNCONFLICT for as long as
the recall is outstanding.
Currently, we may end up livelocking, causing the layout to eventually
be forcibly revoked.
Fixes: bf0291dd2267 ("pNFS: Ensure LAYOUTGET and LAYOUTRETURN are properly serialised")
Cc: stable@vger.kernel.org
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/ynl.py')
0 files changed, 0 insertions, 0 deletions