The patch titled i386: extra checks in show_registers() has been added to the -mm tree. Its filename is i386-extra-checks-in-show_registers.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: i386: extra checks in show_registers() From: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx> Sometimes thread_info and task_struct get out-of-sync with each other. Printing task.thread_info in show_registers() can help spot this. And when task_struct is corrupt then task.comm can contain garbage, so only print as many characters as it can hold. Signed-off-by: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- arch/i386/kernel/traps.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff -puN arch/i386/kernel/traps.c~i386-extra-checks-in-show_registers arch/i386/kernel/traps.c --- a/arch/i386/kernel/traps.c~i386-extra-checks-in-show_registers +++ a/arch/i386/kernel/traps.c @@ -312,8 +312,9 @@ void show_registers(struct pt_regs *regs regs->esi, regs->edi, regs->ebp, esp); printk(KERN_EMERG "ds: %04x es: %04x ss: %04x\n", regs->xds & 0xffff, regs->xes & 0xffff, ss); - printk(KERN_EMERG "Process %s (pid: %d, threadinfo=%p task=%p)", - current->comm, current->pid, current_thread_info(), current); + printk(KERN_EMERG "Process %.*s (pid: %d, ti=%p task=%p task.ti=%p)", + TASK_COMM_LEN, current->comm, current->pid, + current_thread_info(), current, current->thread_info); /* * When in-kernel, we also print out the stack and code at the * time of the fault.. _ Patches currently in -mm which might be from 76306.1226@xxxxxxxxxxxxxx are i386-let-usermode-execute-the-enter.patch i386-fix-get_segment_eip-with-vm86.patch i386-dont-try-kprobes-for-v8086-mode.patch i386-print-stack-size-in-oops-messages.patch i386-use-c-code-for-current_thread_info.patch i386-extra-checks-in-show_registers.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