linux-kernel - Re: [PATCH 4/5] dump_stack: implement arch-specific hardware description in task dumps

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: <20130402182452.GB6185@htj.dyndns.org>
Date:	Tue, 2 Apr 2013 11:24:52 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	linux-arch@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	"x86@...nel.org" <x86@...nel.org>,
	Richard Henderson <rth@...ddle.net>,
	Russell King <linux@....linux.org.uk>, msalter@...hat.com,
	starvik@...s.com, David Howells <dhowells@...hat.com>,
	Tony Luck <tony.luck@...el.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	takata@...ux-m32r.org, Geert Uytterhoeven <geert@...ux-m68k.org>,
	james.hogan@...tec.com, Michal Simek <monstr@...str.eu>,
	Ralf Baechle <ralf@...ux-mips.org>, jonas@...thpole.se,
	rkuo@...eaurora.org, Martin Schwidefsky <schwidefsky@...ibm.com>,
	liqin.chen@...plusct.com, David Miller <davem@...emloft.net>,
	Paul Mundt <lethal@...ux-sh.org>, vgupta@...opsys.com,
	Chris Zankel <chris@...kel.net>,
	Chris Metcalf <cmetcalf@...era.com>,
	ysato@...rs.sourceforge.jp, Guan Xuetao <gxt@...c.pku.edu.cn>,
	jdike@...toit.com
Subject: Re: [PATCH 4/5] dump_stack: implement arch-specific hardware
 description in task dumps

Hello,

On Mon, Apr 01, 2013 at 12:11:17PM -0600, Bjorn Helgaas wrote:
> > +       dump_stack_set_arch_desc("%s %s%s%s", vendor, product,
> > +                                board ? "/" : "", board ? board : "");
> > +}
> 
> Should this be combined or made consistent with dmi_dump_ids()?  They
> look almost the same but not quite (no BIOS version here).

Yeah, that actually would be more useful.  It'd likely be too long
tho.  We can separate it out into its own line which one of the x86
debug paths is doing anyway.  I'll look into it.

Thanks.

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