Windows use a read/write lock (ERESOURCE) per OBJECT_TYPE. BTW: windows
has an internal function BOOL ObReferenceObjectSafe, which tells if the
referencing succeded or not, while the ObReferenceObject is a VOID. Its
probably unrelated thou.
Hartmut Birr wrote:
Hi,
I can fix my problem by protecting the access to some entries of the
object header with a global spinnlock, but I doesn't like this. Has
anyone a better idea?
- Hartmut