linux-kernel - Re: Re-implement MCE log ring buffer as per-CPU ring buffer

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:	Mon, 27 Apr 2009 15:49:56 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Robert Richter <robert.richter@....com>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andi Kleen <ak@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Subject: Re: Re-implement MCE log ring buffer as per-CPU ring buffer

On Fri, 2009-04-24 at 21:36 +0800, Steven Rostedt wrote:
> On Fri, 24 Apr 2009, Robert Richter wrote:
> > > 
> > > It seems that ring_buffer is not NMI-safe, while mcelog buffer will be
> > > used in NMI context and interrupt context. When will ring_buffer to be
> > > NMI-safe?
> > 
> > You can use it in nmi context with separate read and write
> > buffers. See this patch description:
> > 6dad828b76c7224a22ddc9ce7aa495d994f03b31
> > 
> > Not sure if somebody will make the ring_buffer non-locking.
> 
> It already is ;-)
> 
> I've put in for a patent application on the algorithm so I must wait till 
> it is processed before I can release the code.

When will it be merged by mainline kernel? Do you have a plan?

We do have some scalability issues of current mcelog implementation, and
hopes that can be solved as soon as possible, perhaps for 2.6.31?

Best Regards,
Huang Ying


Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)