linux-kernel - Re: Make the 32 bit Frame Pointer backtracer fall back to traditional

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Jan 2008 07:15:01 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Harvey Harrison <harvey.harrison@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Make the 32 bit Frame Pointer backtracer fall back to
 traditional

On Thu, 10 Jan 2008 13:46:06 +0100
Ingo Molnar <mingo@...e.hu> wrote:

> > Arjan, I've been doing some work on traps_32.c porting over the 
> > oops_begin()/oops_end()/_die() arrangement from traps_64.c and then 
> > use it in unifying some more parts of fault.c.
> 
> i've got that applied and it did not seem to interact with Arjan's
> code.
> 
> > If you have other work in this area, I'll hold off until your stuff 
> > goes in...feel free to send me any work in progress stuff and I can 
> > try to coordinate with you.
> 
> i'll yell if anything clashes.


I have a few outstanding things but just go ahead; if you get there first I'll
resolve conflicts, if I get there first.. you'll have to ;-) It's not a big deal,
I'm trying to keep my changes to these areas really self contained small steps
because of the fragility (and because it's just a good idea in general), so any
clashes should also be easy to resolve either way

-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/