linux-kernel - Re: Fw: Re: 2.6.18-rc2-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20060728103826.GB75067@muc.de>
Date:	Fri, 28 Jul 2006 12:38:26 +0200
From:	Andi Kleen <ak@....de>
To:	Jan Beulich <jbeulich@...ell.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...l.org>
Subject: Re: Fw: Re: 2.6.18-rc2-mm1

On Fri, Jul 28, 2006 at 10:56:16AM +0100, Jan Beulich wrote:
> >>> Andrew Morton <akpm@...l.org> 28.07.06 10:19 >>>
> >
> >More unwinder problems.  Seems to be specific to -mm.
> >(Followups on-list are preferred, thanks).
> 
> That's another of the lose ends - while Andi and I had decided to put
> a proper stack frame in place for the switch to the irq stack in the
> interrupt macro, we had forgotten about doing something similar for
> call_softirq() - as the code is written currently, there simply is now
> way of annotating the code properly. If Andi is agreeable to this,
> then I'll just change the code so that it'll have a proper stack frame.

Fine by me. I'll just fix it up.

> 
> The recursive traces appear to result from the fact that when we
> did the change to the interrupt macro, we neglected the fact that
> show_trace() expects to find the old stack pointer as the very first
> item on the interrupt stack, which isn't the case anymore. The value
> of where the subsequent stack access fails is a little strange, though.
> Making this assumption be true again would, however, require adding
> a push to both the interrupt macro and call_softirq. I'm afraid Andi's
> not going to be too happy about that, but on the other hand I can't
> see any other possible way that would get away without adding
> some code to these paths.

I can just add the push.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/