Re: Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- From: Mark Roddy <markr@xxxxxxxxxxxxxx>
- Date: Tue, 25 Apr 2006 10:53:05 -0400
Don Burn wrote:
You are using one OldIrql globally, the OldIrql variable should be a local variable on the stack. I suspect there are other problems but that is the obvious first one. For that matter why are you allocating these at all, KIRQL and KSPIN_LOCK are both <= sizeof (PULONG) ?Yeah like Callers of KeDelayExecutionThread must be running at IRQL <= APC_LEVEL.
The test is broken. The OP cannot "sleep" with a spinlock held. Driver verifier, as always, would have nipped this thread in the bud.
.
- References:
- Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- From: Rohit
- Re: Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- From: Don Burn
- Re: Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- From: Rohit
- Re: Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- From: Don Burn
- Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- Prev by Date: Re: Hi
- Next by Date: Re: How to install device filter driver for HID keyboard?
- Previous by thread: Re: Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- Next by thread: Re: Help me for a typical problem regarding KeAquireSpinLock which is not Locking other Thread in Same CPU
- Index(es):
Relevant Pages
|