diff options
| author | Len Brown <len.brown@intel.com> | 2006-07-07 20:11:07 -0400 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2006-07-09 15:19:44 -0400 |
| commit | ab8aa06a5c0b75974fb1949365cbb20a15cedf14 (patch) | |
| tree | 8498b3b3222198c45fa322b6fdd3215687dc30e4 /drivers/acpi/executer | |
| parent | 120bda20c6f64b32e8bfbdd7b34feafaa5f5332e (diff) | |
| download | linux-ab8aa06a5c0b75974fb1949365cbb20a15cedf14.tar.bz2 | |
ACPI: acpi_os_get_thread_id() returns current
Linux mutexes and the debug code that that reference
acpi_os_get_thread_id() are happy with 0.
But the AML mutexes in exmutex.c expect a unique non-zero
number for each thread - as they track this thread_id
to permit the mutex re-entrancy defined by the ACPI spec.
http://bugzilla.kernel.org/show_bug.cgi?id=6687
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers/acpi/executer')
| -rw-r--r-- | drivers/acpi/executer/exmutex.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/acpi/executer/exmutex.c b/drivers/acpi/executer/exmutex.c index d8ac2877cf05..3a39c2e8e104 100644 --- a/drivers/acpi/executer/exmutex.c +++ b/drivers/acpi/executer/exmutex.c @@ -267,9 +267,9 @@ acpi_ex_release_mutex(union acpi_operand_object *obj_desc, && (obj_desc->mutex.os_mutex != ACPI_GLOBAL_LOCK)) { ACPI_ERROR((AE_INFO, "Thread %X cannot release Mutex [%4.4s] acquired by thread %X", - walk_state->thread->thread_id, + (u32) walk_state->thread->thread_id, acpi_ut_get_node_name(obj_desc->mutex.node), - obj_desc->mutex.owner_thread->thread_id)); + (u32) obj_desc->mutex.owner_thread->thread_id)); return_ACPI_STATUS(AE_AML_NOT_OWNER); } |