linux-kernel - Re: [PATCH] x86: don't call dump_stack() from arch_trigger_all_cpu_backtrace

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: <4D5E350602000078000329C7@vpn.id2.novell.com>
Date:	Fri, 18 Feb 2011 07:59:50 +0000
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	<tglx@...utronix.de>, <linux-kernel@...r.kernel.org>,
	<hpa@...or.com>
Subject: Re: [PATCH] x86: don't call dump_stack() from
	 arch_trigger_all_cpu_backtrace_handler()

>>> On 18.02.11 at 08:44, Ingo Molnar <mingo@...e.hu> wrote:

> * Jan Beulich <JBeulich@...ell.com> wrote:
> 
>> show_regs() already prints two(!) stack traces, [...]
> 
> That ought to get fixed as well, right?

Yes, I'm intending to send a patch for that as a follow-up.

Jan

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