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:	Sat, 23 Sep 2006 16:34:33 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	Richard J Moore <richardj_moore@...ibm.com>
cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: score-boarding [was Re: [PATCH] Linux Kernel Markers]

On Thu, 21 Sep 2006, Richard J Moore wrote:
> 
> It can for another reason - score-boarding: that's where a byte being
> stored assumes intermediate values due to the bits not being set
> simultaneously. Generally this doesn't cause a problem because data across
> processors is serialised for update by mutexes. However, when applied to
> code all sorts of interesting instructions can execute before the bits
> settle down. I haven't heard of this troubling Intel, but it does occur on
> some current architectures.

I'd not heard of this phenomenon, and it worries me.  There are places
in kernel code where we peek at some volatile variable (perhaps a long)
without locking, and expect to see it in any one of several well-defined
states.  Are you saying that there are architectures supported by Linux,
on which we might see an "impossible" mix of states, due to score-boarding?

Hugh
-
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