Re: Error in save_stack_trace() on x86_64?
From: Vegard Nossum
Date: Sun May 18 2008 - 16:23:57 EST
On Sun, May 18, 2008 at 8:52 PM, Arjan van de Ven <arjan@xxxxxxxxxxxxxxx> wrote:
> On Sun, 18 May 2008 20:31:18 +0200
>> Is the error obvious from the stack-trace I posted above? This is not
>> really my field, so I might easily miss it :-)
> unfortunately I don't really have time today to take a detailed look
> (social obligations), but the trick is to follow where EBP (rBP) is
That's perfectly okay, I regard all help as a bonus :-D
There seems to be something odd going on here:
ffffffff80877bc8: ffffffff80877c98 <--- this points to the frame below
ffffffff80877c98: 000000008020bb59 <--- but this pointer is invalid!
And the invalid pointer should have been ffffffff80877f48:
ffffffff80877f48: ffffffff80877f78 <---
[<ffffffff80882b35>] ? start_kernel+0x245/0x340
which is where the page fault came from.
It seems to me error_exit() called do_page_fault(), but that
do_page_fault() did not push the %rbp, or it was overwritten later.
(But how can it then be restored correctly when the function returns?)
I think this is the relevant code (from arch/x86/kernel/entry_64.S):
movq ORIG_RAX(%rsp),%rsi /* get error code */
/* ebx: no swapgs flag (1: don't need swapgs, 0: need it) */
where that "call *%rax" would push the (return) address of error_exit
on the stack and go into do_page_fault().
It seems that do_page_fault() is doing the right thing, however:
ffffffff8062b030: 55 push %rbp
ffffffff8062b031: 48 89 e5 mov %rsp,%rbp
ffffffff8062b034: 53 push %rbx
ffffffff8062b035: 48 81 ec b8 00 00 00 sub $0xb8,%rsp
so my current theory is that the entry is overwritten later.
So what is the value 000000008020bb59 (from the erronous stack entry)?
It certainly looks like the lower half of an address to me.
And indeed, looking this up gives me:
ffffffff8020bb59: 48 cf iretq
In any case, I think we can safely assume that the stack tracer itself
is perfectly okay, and that the error is actually in how the stack is
handled just before/after the actual call to do_page_fault(). Does
anybody actually know how this code all works? It is admittedly
probably not the most critical error in the kernel, but it would be
nice to have this sorted out. Ingo, hpa...?
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/