linux-kernel - [026/126] spinlocks and preemption points need to be at least compiler barriers

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: <20130507035845.231490192@goodmis.org>
Date:	Mon, 06 May 2013 23:57:38 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Cc:	Steven Rostedt <srostedt@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: [026/126] spinlocks and preemption points need to be at least compiler
 barriers

View attachment "0026-spinlocks-and-preemption-points-need-to-be-at-least-.patch" of type "text/plain" (6769 bytes)