posix.renameW: Handle DIRECTORY_NOT_EMPTY more generally #19804
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.
Before this commit, the DIRECTORY_NOT_EMPTY/FILE_IS_A_DIRECTORY/NOT_A_DIRECTORY statuses were assumed only to be possible when using
FILE_RENAME_INFORMATION_EX
andFILE_RENAME_POSIX_SEMANTICS
, but that has empirically been shown to be false; a networked samba share can return the DIRECTORY_NOT_EMPTY status fromFILE_RENAME_INFORMATION
(which doesn't supportFILE_RENAME_POSIX_SEMANTICS
).FILE_IS_A_DIRECTORY
andNOT_A_DIRECTORY
were not proven to be possible (from my testing,OBJECT_NAME_COLLISION
is returned when trying to name a file onto a directory or vice versa), but they were also moved to the outer switch just in case.Fixes #19785