Should i worry about Opportunistic Locks?

NTDEV
1

Hi All,

I am writing mini-filter file system driver to track file precreate and used to send same file path and process id (which is accessing file) to my service then service makes a copy of an input file and returns the call.

So for this kind of functionality do i need to take care of Opportunistic Locks or i can ignore them.

Thanks

2

That’s a really broad question. All file system filters have to deal with
oplocks, at least from the perspective that they exist and are used heavily
in Windows. In addition, if you’re opening files in a filter you will very
likely trigger oplock breaks. This is fine, unless you do something to hold
up the acknowledgement (in which case you’ll deadlock).

Sooooo the answer is: maybe, maybe not. What I *can* say is that if you’re
writing a file system filter you need to understand oplocks, whether you’re
directly involved with them or not.

(Also, file system filter questions are best left for NTFSD)

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@ntdev…

Hi All,

I am writing mini-filter file system driver to track file precreate and used
to send same file path and process id (which is accessing file) to my
service then service makes a copy of an input file and returns the call.

So for this kind of functionality do i need to take care of Opportunistic
Locks or i can ignore them.

Thanks