Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Byte-range locks of expired clients not ignored #112

Open
kofemann opened this issue Jan 25, 2022 · 0 comments
Open

Byte-range locks of expired clients not ignored #112

kofemann opened this issue Jan 25, 2022 · 0 comments

Comments

@kofemann
Copy link
Member

As resources allocated by expired clients are reclaimed by a periodically running cleanup thread, there are situations when a lock by a valid client denied due to conflicting lock of an expired client (pynfs test COUR2 testLockSleepLock).

This should be fixed in AbstractLockManager#lock method by checking , that conflict lock is held by a valid client.

@kofemann kofemann changed the title Byte-range locks og expired clients not ignored Byte-range locks of expired clients not ignored Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant