Bug 5334
Summary: | No exception when Serialized Method is run after the higher level mutex acquiring | ||
---|---|---|---|
Product: | ACPI | Reporter: | Valery A Podrezov (Valery.A.Podrezov) |
Component: | ACPICA-Core | Assignee: | Valery A Podrezov (Valery.A.Podrezov) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | acpi-bugzilla |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | ASL code to reproduce bug. |
Description
Valery A Podrezov
2005-09-30 06:12:34 UTC
Created attachment 6194 [details]
ASL code to reproduce bug.
Serialized Method doesn't follow SyncLevel transition rule (17.5.79 Mutex).
Namely, invocation of the Method declared as a Serialized one doesn't cause
exception in case it is declared for the level lower than the current
synchronization level is. This contradicts with the rule mentioned above.
Actions reproducing the bug (see Method md8d of attached demo).
1. Mutex of level 1 is acquired.
2. Serialized Method specified with 0 SyncLevel is invoked.
3. Exception AE_AML_MUTEX_ORDER is expected in this case
due to the lower synchronization level of Method which
is invoked after acquiring the higher level mutex.
4. But, and this is a bug, no exception occurs.
INTERNAL BUG NUMBER
150
Fixed in 20060623 version of ACPICA. ACPICA 20060707 shipped in Linux-2.6.18 closed. |