RE: Anything to be aware of when calling ZwOpenSemaphore,- ZwOpenMutant, ZwOpenEvent?

Have you proper headers of this routines?
Another question: could you show me how you’re using them?

Example:
HANDLE Handle;
NTSTATUS Status;
UNICODE_STRING Name;
OBJECT_ATTRIBUTES ObjAttr;

RtlInitUnicodeString(&Name, L"\NameOfSemaphore");
InitializeObjectAttributes(&ObjAttr, &Name, 0, NULL, NULL);

Status = NtOpenSemaphore(&Handle, SEMAPHORE_ALL_ACCESS, &ObjAttr);
if (!NT_SUCCESS(Status)) …

My definitions are here:
<>
Paul
> -----P?vodn? zpr?va-----
> Od: xxxxx@erinet.com [SMTP:xxxxx@erinet.com]
> Odesl?no: 5. kv?tna 2000 18:29
> Komu: File Systems Developers
> Kopie: xxxxx@curriculum.com
> P?edm?t: [ntfsd] Anything to be aware of when calling
> ZwOpenSemaphore, ZwOpenMutant, ZwOpenEvent?
>
> Hi all,
>
> I have a memory mapped object protected by an implementation using
> the above to implement single writer multiple readers.
>
> This object is shared by both kernel mode driver and multiple user
> mode applications.
>
> Right now if I enable these Native API synchronization calls, I got
> random page fault that I was unable to pinpoint the exact location
> of the fault.
>
> If I disable these calls, then everything is fine.
>
> I am suspecting these calls may somehow raise IRQL that cause the
> problem.
>
> I am looking for possible causes and workaround !
>
> Thanks,
>
> Jack Cheng
> (curriculum corp.)
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@sodatsw.cz
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)