Re: [ros-svn] [hbirr] 20793: - We cannot access the OwnerTable without locking the resource.

[Hartmut Birr]

[e-mail] wrote:
> We cannot access the OwnerTable without locking the resource.
> The shared waiters may wait also on the semaphore. It makes no sense to boost a waiting thread.
> The thread header is initialized like KeWaitForSingleObject (?, ?, ?, TRUE, ?). During the boost, 
> possible the dispatcher lock is released but the thread block (WaitNext) isn't changed.
>
> Updated files:
> trunk/reactos/ntoskrnl/ex/resource.c
>
> Ros-svn mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-svn

Oops, I've copied the wrong commit message. The correct is:

- We cannot access the OnerTable without locking the resource.
- The shared waiters may wait also on the semaphore. It makes no sence
to boost a waiting thread.
- The thread header is initialized like KeWaitForSingleObject (?, ?, ?,
TRUE, ?). During the boost,
  possible the dispatcher lock is released but the thread block
(WaitNext) isn't changed.

- Hartmut

[Hartmut Birr]

2006/1/12, Hartmut Birr [e-mail]:
> Oops, I've copied the wrong commit message. The correct is:

Copied the wrong commit message for a second time. The correct is:
- Disabled the priority boosting (Read the comments inside the file).
- Return FALSE if we cannot acquire the resource in
ExAcquireResourceSharedLite immediatley and if waiting isn't allowed.
This will fix bug #1256.
- Don't trust that the build-in owner is always free.

- Hartmut