linux-kernel - Re: [PATCH 03/20] x86, mce: Add persistent MCE event

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: <87lj50vq0s.fsf@gmail.com>
Date:	Wed, 10 Nov 2010 16:15:47 -0500
From:	Ben Gamari <bgamari@...il.com>
To:	Borislav Petkov <bp@...64.org>, acme@...radead.org,
	fweisbec@...il.com, mingo@...e.hu, peterz@...radead.org,
	rostedt@...dmis.org
Cc:	linux-kernel@...r.kernel.org,
	Borislav Petkov <borislav.petkov@....com>
Subject: Re: [PATCH 03/20] x86, mce: Add persistent MCE event

On Thu,  4 Nov 2010 16:36:39 +0100, Borislav Petkov <bp@...64.org> wrote:
> From: Borislav Petkov <borislav.petkov@....com>
> 
> Add the necessary glue to enable the mce_record tracepoint on boot
> turning it into a persistent event. This exports the MCE buffer
> read-only to a userspace daemon which will hook into it through debugfs
> when booting is finished.
> 
While MCE technically is a diagnostics service, do we want to start
adding dependencies on debugfs in long-running, common-place daemons? I
was under the impression we were to avoid using debugfs for anything
other than values for one-off debugging.

Cheers,

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