Actually we may want to tweak stat() to not complain for a file with such a state.
That will still leave is with a race condition won't it? It'll just be much smaller? The file could go into STATUS_DELETE_PENDING between the call to stat() and the call to sendFile()/allocateFile().
Maybe that's an acceptable difference? If not, we also need to teach AllocateFile() about the error.
If we're happy with just stat, it looks like we will have to add it to pgwin32_safestat().
I don' t have a working window sbox for testing ATM (yeah yeah, it's on my magic todo), but can someone confirm if calling stat() on such a deleted flie sets the errorcode so it can be checked with GetLastError() *as well* as setting errno? IIRC those functions do, but it needs to be checked. If so, the attached might work? If not, then we need an extra call to GetFileAttributesEx(), or rearrange those calls in a way to trap errors there.
