linux-kernel - Re: [RESEND][PATCH 1/2] stacktrace: add saved stack traces to backtrace self-test

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]

Message-ID: <20080627160821.GA30232@elte.hu>
Date:	Fri, 27 Jun 2008 18:08:21 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RESEND][PATCH 1/2] stacktrace: add saved stack traces to
	backtrace self-test


* Vegard Nossum <vegard.nossum@...il.com> wrote:

> Hi,
> 
> I'm not really sure to whom this goes. It seems that the original code 
> came through the x86 tree, although the code itself seems to be 
> entirely generic.

given that i've written the generic stacktrace code for lockdep, i guess 
it comes to me - the only question would be into which branch ;-)

fortunately there's already a tip/core/stacktrace topic, hosting a 
change for you as well:

 Ingo Molnar (1):
       debugging: make stacktrace independent from DEBUG_KERNEL

 Johannes Berg (1):
       stacktrace: don't crash on invalid stack trace structs

 Vegard Nossum (1):
       stacktrace: print_stack_trace() cleanup

i'll queue this one up there.

	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/