NFSD: Block DESTROY_CLIENTID only when there are ongoing async COPY operations

Browse source

Currently __destroy_client() consults the nfs4_client's async_copies
list to determine whether there are ongoing async COPY operations.
However, NFSD now keeps copy state in that list even when the
async copy has completed, to enable OFFLOAD_STATUS to find the
COPY results for a while after the COPY has completed.

DESTROY_CLIENTID should not be blocked if the client's async_copies
list contains state for only completed copy operations.

Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

...

This commit is contained in:

Chuck Lever 2024-10-31 09:40:06 -04:00

parent 5c41f32147

commit b44ffa4c4f

3 changed files with 32 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

30

fs/nfsd/nfs4proc.c

View file

2

fs/nfsd/nfs4state.c

View file

1

fs/nfsd/state.h

View file