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]
Message-ID: <cc96a5040707121428j6c03fb6eyd27685a9f172ac23@mail.gmail.com>
Date:	Thu, 12 Jul 2007 14:28:25 -0700
From:	"Tim Hockin" <thockin@...gle.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	"Joshua Wise" <jwise@...gle.com>, akpm@...gle.com,
	linux-kernel@...r.kernel.org, "Mike Waychison" <mikew@...gle.com>
Subject: Re: [x86_64 MCE] [RFC] mce.c race condition (or: when evil hacks are the only options)

On 7/12/07, Andi Kleen <ak@...e.de> wrote:

> > -- there may be other edge cases other than
> > this one. I'm actually surprised that this wasn't a ring buffer to start
> > with -- it certainly seems like it wanted to be one.
>
> The problem with a ring buffer is that it would lose old entries; but
> for machine checks you really want the first entries because
> the later ones might be just junk.

Couldn't the ring just have logic to detect an overrun and stop
logging until that is alleviated?  Similar to what is done now.  Maybe
I am underestimating it..
-
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