What is behind RENAME via RDR?

NTFSD
1

If I rename a local file say C:\share\abc.txt to xyz.txt on the same
directory, my filter driver can catch a CREATE request for C:\share\xyz.txt
with SL_OPEN_TARGET_DIRECTORY.
Then I make a network share directory for C:\share and attach it to a second
computer.
If I rename the same file on the shared directory from the second computer,
there is no CREATE request with SL_OPEN_TARGET_DIRECTORY comes to my filter.
Can someone explain this difference?

Thanks so much,

Shangwu

2

What RDR does is, at best, unpredictable. It is trying to implement a
pretty ‘interesting’ protocol as fast as it can (wasn’t there a talk on the
original IFS videos about RDR/SRV and entitled “Performance optimization by
incorrect operation?”).

Anyway it’s been my experience that RDR and SRV can do some non-intuitive
things. In this case it might well be that you are being issued with an
absolute rename (that is, one with a NULL
FileReanemInformation->RootDirectory or it’s irpSp equivalent)

3

Thanks Rod for your input.

Shangwu

“Rod Widdowson” wrote in message
news:xxxxx@ntfsd…
> What RDR does is, at best, unpredictable. It is trying to implement a
> pretty ‘interesting’ protocol as fast as it can (wasn’t there a talk on
> the original IFS videos about RDR/SRV and entitled “Performance
> optimization by incorrect operation?”).
>
> Anyway it’s been my experience that RDR and SRV can do some non-intuitive
> things. In this case it might well be that you are being issued with an
> absolute rename (that is, one with a NULL
> FileReanemInformation->RootDirectory or it’s irpSp equivalent)
>
>