linux-kernel - Re: [PATCH 1/2] Add HW_ERR printk prefix for hardware error logging

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]

Date:	Fri, 11 Jun 2010 09:18:15 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...ux.intel.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] Add HW_ERR printk prefix for hardware error logging

On Fri, 2010-06-11 at 07:46 +0800, Andrew Morton wrote:
> On Tue, 08 Jun 2010 14:35:38 +0800
> Huang Ying <ying.huang@...el.com> wrote:
> 
> > This makes hardware error related log in printk log more explicit. So
> > that the users can report it to hardware vendor instead of LKML or
> > software vendor.
> > 
> 
> Spose so.  Some additional words explaining why you think this would
> result in an improved kernel would help here.  Are you seeing
> misdirected problem reports?  Are we missing out on opportunities to
> fix hardware?  What is driving for this change?  Will it bring out some
> improvement in something which you're seeing within Intel or was it
> just a random hey-lets-try-this thing?

It is said by Andi Kleen that many users report Machine Check hardware
error message as software error to him or software vendor instead of as
hardware error to hardware vendor. This does not help much for the users
to resolve their problem. So I think it is better to make the kernel
hardware error log more explicit for these users.

Best Regards,
Huang Ying


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