linux-kernel - Re: [PATCH] x86_64: print DMI info in the oops trace

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

Message-ID: <20090204211243.GJ22608@elte.hu>
Date:	Wed, 4 Feb 2009 22:12:43 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Kyle McMartin <kyle@...radead.org>
Cc:	mingo@...hat.com, arjan@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64: print DMI info in the oops trace


* Kyle McMartin <kyle@...radead.org> wrote:

> From: Kyle McMartin <kyle@...hat.com>
> 
> This patch echoes what we already do on 32-bit since
> 90f7d25c6b672137344f447a30a9159945ffea72, and prints the DMI
> product name in show_regs, so that system specific problems can be
> easily identified.
> 
> Signed-off-by: Kyle McMartin <kyle@...hat.com>

Applied to tip/x86/urgent, thanks Kyle!

> Noticed we weren't doing this on x86_64 while backporting this change to 
> 2.6.27 for Fedora... Any reason for it?

No reason, simple oversight. Also, a good 75% of the x86 testers are still 
on 32-bit and covering the main volume is what such changes tend to aim for 
primarily. The remaining 25% is nice to have too :)

If you notice such things - or if you have anything in the Fedora srpm that 
you think is worth mainlining, just drop us a patch - it's apprecitated.

	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/