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  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:	Thu, 10 Jul 2014 13:42:22 +0200
From:	Borislav Petkov <>
To:	Havard Skinnemoen <>
Cc:	Tony Luck <>,
	Linux Kernel <>,
	Ewout van Bekkum <>,
	linux-edac <>
Subject: Re: [PATCH 1/6] x86-mce: Modify CMCI poll interval to adjust for
 small check_interval values.

+ linux-edac.

On Wed, Jul 09, 2014 at 02:24:31PM -0700, Havard Skinnemoen wrote:
> > > The CMCI poll interval was updated to pick the minimum interval between
> > > the original 30 seconds and the check_interval divided by 8 (minimum of
> > > 3 polls).
> >
> > Why min 3 polls? How do you come up with exactly that frequency?
> The idea is that if we make it equal to check_interval, it might
> bounce back and forth a lot. So we need to divide by something, and 8
> seems like a nice, safe value, and it seems to work well. We're not
> opposed to considering other values, of course (e.g. 2 and 4 might
> work well too, but with somewhat higher risk of ping-ponging).

Yep, this is exactly why I'm asking about your use case. Because if we
set it to any number, someone down the line will appear and say that
this doesn't suit her/his needs.

So, I'm thinking more in the direction of controlling it settings, maybe
even restricting check_interval and the CMCI poll interval, relative to
each other maybe, but still configurable with the max flexibility.

For that we'll need to answer questions like

* Which min value is sane?
* Do check_interval and CMCI poll interval need to be related at all?
* Which max value makes sense?
* What about check_interval, do we want to touch that too?

Just throwing out a bunch of questions, off the top of my head, to get
some opinions/rants, etc.

> I'm not entirely sure. At some point, it ended up that way, and it
> broke in non-obvious ways, so we wanted to fix it.

Right, so if we restrict it, the fix is even simpler. Unless you have a
more valid use than "[a]t some point, it ended up that way... " :-)

> We will definitely take a look, thanks. Looks interesting, though it's
> not always obvious what works for us until we actually go and try it.

Cool, thanks.


Sent from a fat crate under my desk. Formatting is fine.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists