Skip to content

[FileSystem] ReAdd check for same device#34343

Merged
mdh1418 merged 1 commit intodotnet:masterfrom
mdh1418:mdhwang/filesystemwatcher_add_device_check
Mar 31, 2020
Merged

[FileSystem] ReAdd check for same device#34343
mdh1418 merged 1 commit intodotnet:masterfrom
mdh1418:mdhwang/filesystemwatcher_add_device_check

Conversation

@mdh1418
Copy link
Member

@mdh1418 mdh1418 commented Mar 31, 2020

Fixes #34330

Copy link
Member

@danmoseley danmoseley left a comment

Choose a reason for hiding this comment

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

thanks

@danmoseley
Copy link
Member

It seems to me that this does not meet the bar for servicing 3.1 since presumably the chance of a inode collision is vanishingly small, and it would only show up when moving a file to itself.

@mdh1418 mdh1418 merged commit 8876693 into dotnet:master Mar 31, 2020
@mdh1418 mdh1418 deleted the mdhwang/filesystemwatcher_add_device_check branch March 31, 2020 21:47
@joshudson
Copy link
Contributor

@danmosemsft : That race condition isn't vanishingly small, but not for the reason you think it is. The real race happens when two processes call File.Move(..., overwrite = false) with the same name in the second argument but a different name in the first argument (unique name generator--the guy who fails will increment a counter and try again). I've hit that race. The real fix is in #31228

@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Change in FileSystem.Unix.File.Move possibly introduced bug

5 participants