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

Fix a potential crash in moves #7726

Merged
merged 3 commits into from
Feb 10, 2020
Merged

Fix a potential crash in moves #7726

merged 3 commits into from
Feb 10, 2020

Conversation

ogoffart
Copy link
Contributor

@ogoffart ogoffart commented Feb 6, 2020

Issue #7722

I was not able to reproduce the problem (the new tests don't reproduce it)
But this is just the most plausible explanation for this crash.

This was an attempt to reproduce #7722, but this actually does not
reproduce it
…edJob

Issue #7722

I was not able to reproduce the crash, but this is seen in the crash
reporter.

The crash occurs because the ENFORCE in that function is reached. One way
this could happen is because findAndCancelDeletedJob would be called
for the same path multiple times. Potentially this could perhaps be caused
by duplicated inodes are duplicated. But this is hard to test.
@ogoffart ogoffart changed the base branch from master to 2.6 February 6, 2020 10:17
@ogoffart ogoffart requested a review from TheOneRing February 6, 2020 10:17
Copy link
Contributor

@TheOneRing TheOneRing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks sane

@ogoffart ogoffart merged commit 9854c6d into 2.6 Feb 10, 2020
@delete-merged-branch delete-merged-branch bot deleted the fix-7722 branch February 10, 2020 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants