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:	Sat, 12 Jan 2008 07:30:37 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, tglx@...x.de, hpa@...or.com
Subject: Re: [patch 0/8] Series to improve the x86 backtracing code


* Arjan van de Ven <arjan@...radead.org> wrote:

> this patch series improves the x86 backtracing code in the following ways:
> 1) Fix a bad bug in x86 (32 bit) FRAME_POINTER backtracing (2.6.24 material)
> 2) Add the capability to mark a backtrace entry as reliable / unreliable
> 3) Change the x86 (32 bit) FRAME_POINTER backtracing to use the normal backtrace but use the frames
>    as guidance to the reliability of the backtrace entries
> 4) Patch to capture the EBP register earlier in the backtrace callchain to get a better FRAME_POINTER
>    based backtrace
> 5) Split the x86 (64 bit) backtrace code up similar to the 32 bit code by turning a macro into a function
> 6) Enable FRAME_POINTER backtracing on 64 bit similar to the 32 bit patch in number 3
> 7) Add a simple self-test module for backtraces (will move to tests/ later when that gets merged)
> 8) Add the feature to x86 64bit to print a set of bytes prior to the current EIP in the Code: line
>    (already present in 32 bit)

thanks, i've applied your new series to x86.git. (Note that i had to 
move around some of the changes to make the series bisectable.)

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ