It appears that at least on WS03, NTFS calls ZwCreateFile with TopLevelIrp
!= 0. The unfortunate side effect of this is a call to
FltGetFileNameInformation for a normalized name during post-CREATE
processing fails with STATUS_FLT_INVALID_NAME_REQUEST. The ZwCreateFile call
comes out of a routine called NtfsSetReparsePoint. It looks like it was part
of a volume mount operation and/or creating a mount point?
Question is: Is there anyway out of this situation – creating a worker
thread to resolve the name, perhaps leading to deadlock doesn’t seem to be
the right way to avoid this case.
/ted