Fix deadlock in layered FS for migrated files#903
Merged
jaybosamiya-ms merged 2 commits intoJun 5, 2026
Conversation
Contributor
Author
|
@microsoft-github-policy-service agree company="Microsoft" |
jaybosamiya-ms
approved these changes
Jun 5, 2026
jaybosamiya-ms
left a comment
jaybosamiya-ms
left a comment
Member
There was a problem hiding this comment.
Thanks Shai! Good catch, let's chat more about this IRL soon. I'll mildly tweak the PR title/description, since that's what the merge queue uses as the commit message, and then will hit merge shortly.
jaybosamiya-ms
changed the title
Member
|
@jaybosamiya-ms should we cherry pick this one to ulitebox? |
Member
|
Answered IRL, but briefly: due to upcoming changes to layered FS, we don't need to cherry pick this one over rn |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix deadlock in layered FS where the
node_info_lookuplock is read-acquired and then write-acquired