The patch titled
rtmutex debug: printk correct task information
has been added to the -mm tree. Its filename is
rtmutex-debug-printk-correct-task-information.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Print the information of the current task rather than some random picked task
information.
Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
kernel/rtmutex.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN kernel/rtmutex.c~rtmutex-debug-printk-correct-task-information kernel/rtmutex.c
--- 25/kernel/rtmutex.c~rtmutex-debug-printk-correct-task-information Wed Apr 26 14:24:26 2006
+++ 25-akpm/kernel/rtmutex.c Wed Apr 26 14:24:26 2006
@@ -180,7 +180,7 @@ static int rt_mutex_adjust_prio_chain(ta
prev_max = max_lock_depth;
printk(KERN_WARNING "Maximum lock depth %d reached "
"task: %s (%d)\n", max_lock_depth,
- task->comm, task->pid);
+ current->comm, current->pid);
}
put_task_struct(task);
_
Patches currently in -mm which might be from tglx@xxxxxxxxxxxxx are
git-mtd.patch
cleanup-default-value-of-mtd_pcmcia_anonymous.patch
pi-futex-futex-code-cleanups.patch
pi-futex-introduce-debug_check_no_locks_freed.patch
pi-futex-add-plist-implementation.patch
pi-futex-scheduler-support-for-pi.patch
pi-futex-rt-mutex-core.patch
pi-futex-rt-mutex-core-fix-timeout-race.patch
pi-futex-rt-mutex-docs.patch
pi-futex-rt-mutex-debug.patch
pi-futex-rt-mutex-tester.patch
pi-futex-rt-mutex-futex-api.patch
pi-futex-futex_lock_pi-futex_unlock_pi-support.patch
rtmutex-remove-buggy-bug_on-in-pi-boosting-code.patch
futex-pi-enforce-waiter-bit-when-owner-died-is-detected.patch
rtmutex-debug-printk-correct-task-information.patch
futex-pi-make-use-of-restart_block-when-interrupted.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
