linux-kernel - [PATCH RT 0/3][FYI only] 3.2-rt cpu hotplug fix (hack)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120306023835.775610473@goodmis.org>
Date:	Mon, 05 Mar 2012 21:38:35 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Carsten Emde <C.Emde@...dl.org>,
	Clark Williams <clark.williams@...il.com>
Subject: [PATCH RT 0/3][FYI only] 3.2-rt cpu hotplug fix (hack)

This is an FYI patch set only. It fixes a lot of the races that the
current -rt patch has with stressing hotplug.

Although this patch set (well patch one really) does prove to solve a
lot of the race conditions caused by notifiers waiting on tasks
that may be on the CPU going down, the patch itself is not at the
state that it should be accepted.

I'm posting this only for those that need a current fix while we work
on a real fix. Again, this patch set is an actual fix to several issues
with hotplug. But it makes the code even more hacky and there's
better ways to solve the issues.

I've been running my CPU hotplug stress test and a distcc kernel
compile (-j20) on a 4 way machine for the last 30 minutes (both in a
while loop) and it's still going strong.

This patch set goes on top of 3.2.9-rt15

Have fun,

-- Steve

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