linux-kernel - Re: RAS trace event proto

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]

Date:	Wed, 22 Feb 2012 12:25:03 -0200
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Borislav Petkov <bp@...64.org>
CC:	"Luck, Tony" <tony.luck@...el.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...e.hu>,
	edac-devel <linux-edac@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: RAS trace event proto

Em 22-02-2012 12:05, Borislav Petkov escreveu:
> On Wed, Feb 22, 2012 at 11:32:16AM -0200, Mauro Carvalho Chehab wrote:
> 
>> So, in other words, I think that the _best_ way to represent an MCA
>> type of error is to use an event with the following prototype:
> 
> No, it's not.

Why? It fits with all existing edac drivers, and it seems to fit with
mce_amd, based on the examples you gave.

> 
> And if you're going to repeat yourself for the 100th time as to why,
> don't even bother replying.

Well, a single string is not ok, as it is not easily parseable and it
doesn't allow to use the perf filters.

We need to agree on some trace format that fits, and that covers the
needs by the existing drivers.

I'm ok, if you didn't like the format I've proposed, if you have
a better proposal.

Regards,
Mauro.
--
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/