Re: 2.6.19-rc2-mm1 unwinder issues ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


>>> Badari Pulavarty <[email protected]> 19.10.06 00:36 >>>
>Hi Andi,
>I am not getting stack traces properly on 2.6.19-rc2-mm1 again 
>(on my amd64 box).
>Wondering, if the unwinder code changed again ??

This patch:

>Annotate interrupt frame backlink in interrupt handlers
>Add correct CFI annotation to the backlink on top of the interrupt stack.
>Signed-off-by: Andi Kleen <[email protected]>
> arch/x86_64/kernel/entry.S |    3 +++
> 1 files changed, 3 insertions(+)
>Index: linux/arch/x86_64/kernel/entry.S
>--- linux.orig/arch/x86_64/kernel/entry.S
>+++ linux/arch/x86_64/kernel/entry.S
>@@ -535,6 +535,8 @@ END(stub_rt_sigreturn)
> 1:	incl	%gs:pda_irqcount
> 	cmoveq %gs:pda_irqstackptr,%rsp
> 	push    %rbp			# backlink for old unwinder
> 	/*
> 	 * We entered an interrupt context - irqs are off:
> 	 */
>@@ -1174,6 +1176,7 @@ ENTRY(call_softirq)
> 	incl %gs:pda_irqcount
> 	cmove %gs:pda_irqstackptr,%rsp
> 	push  %rbp			# backlink for old unwinder
> 	call __do_softirq
> 	leaveq

must be reverted for things to work again. Andi, what did you
want to cure with it? Clearly, when rSP isn't the CFA register
anymore, there must not (normally) be adjustments to the
CFA offset. Similarly, when a register was saved already and
it's not its spill location that changes, it must not be marked
as being saved a second time.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at
Please read the FAQ at

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux