Paul Bryan Roberts pbronline-wine@yahoo.co.uk writes:
This patch adds a couple of conformance tests that check 'error' return codes. GetFileSecurity() is expected to be called twice - once to find out how much memory to allocate and again once the memory has been allocated. It seems the Windows implementation is a bit fussy and the implementation of GetFileSecurity() was changed to match.
That's not necessary, unless there's an application that depends on it. Behavior on invalid parameters is usually inconsistent on Windows too, so there's no need to write test cases for that sort of thing.