avoid deadlock: cancel hydration requests coming from itself #6868
Conversation
our current infrastructure will cause a deadlock for any hydration requests coming from desktop files client itself the main thread is responsible for executing the hydration request but if the same thread is already blocked waiting for the hydration to happen, both (open system call and hydration request handling) process will never be completed and wait for each over in a stuck cycle Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
|
/backport to stable-3.12 |
|
/backport to stable-3.13 |
mgallien
deleted the
bugfix/avoidDeadlockWithImplicitHydrationSelfRequests
branch
|
The backport to # Switch to the target branch and update it
git checkout stable-3.12
git pull origin stable-3.12
# Create the new backport branch
git checkout -b backport/6868/stable-3.12
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c5c8f0f1
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/6868/stable-3.12Error: Failed to clone repository: Failed to checkout branches: error: Your local changes to the following files would be overwritten by checkout: Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
AppImage file: nextcloud-PR-6868-c5c8f0f11b134d3643a386f750cf0796a0402077-x86_64.AppImage |
|
our current infrastructure will cause a deadlock for any hydration requests coming from desktop files client itself
the main thread is responsible for executing the hydration request but if the same thread is already blocked waiting for the hydration to happen, both (open system call and hydration request handling) process will never be completed and wait for each over in a stuck cycle