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: <1290659715.2903.299.camel@yhuang-dev>
Date:	Thu, 25 Nov 2010 12:35:15 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Mark Lord <kernel@...savvy.com>
Cc:	huang ying <huang.ying.caritas@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Len Brown <lenb@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Borislav Petkov <bp@...en8.de>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 0/2] Generic hardware error reporting support

On Thu, 2010-11-25 at 10:41 +0800, Mark Lord wrote:
> On 10-11-22 07:29 PM, Huang Ying wrote:
> > On Tue, 2010-11-23 at 07:43 +0800, Mark Lord wrote:
> >> On 10-11-20 08:06 PM, huang ying wrote:
> >>>
> >>> I have no objection to report hardware errors in system logs too. So
> >>> these people can get the information too. I just want to add another
> >>> tool oriented interface too. So that some other users (like cluster
> >>> administrator) can get their work done better too.
> >>
> >> So, use the standard interface for the tool:  syslog.
> >
> > Although it may be possible to extract some information from syslog and
> > parse it in a fault tolerant way, we can only use that human oriented
> > interface for a tool? That sounds like hack.
> 
> No, that sounds like the *NIX programming philosophy.
> 
> You may have already noticed that most *NIX tools store
> and manage data in _text_ form.  That makes it easy to
> understand, easy to parse/process, and generally better
> in almost every respect.

I have no objection to text form interface.  I said printk is not a tool
oriented interface not because it is a text form interface but some
other issues.  For example, messages from different CPU/context may be
interleaved; all kinds information mixed together, without overall
format or meta-data, etc.

> Other platforms (GNOME, MS-Windows) prefer a binary format
> that requires special tools to view/access.  Ugh.

Linux kernel uses binary format interfaces too.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ