https://bugs.winehq.org/show_bug.cgi?id=47833
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |4.17
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- Sounds reasonable to me, though I'm inclined to say that regardless of testing it may be upstreamable directly. While I don't think it's [legally] safe to test what values Windows passes to NtOpenFile(), it's probably reasonable for us to alter behaviour in such a way if it's shown to improve programs.
Moreover, MSDN says that FILE_FLAG_BACKUP_SEMANTICS must be used to open a directory handle [1]. So it may be worth testing whether a similar restriction applies to NtOpenFile(), and, if so, it'd be even easier to justify adding that flag.
[1] https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-create...