linux-kernel - [patch v2 0/4] MTRR rendezvous deadlock fix and cleanups using stop

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: <20110623181925.983511592@sbsiddha-MOBL3.sc.intel.com>
Date:	Thu, 23 Jun 2011 11:19:25 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	mingo@...e.hu, tglx@...utronix.de, hpa@...or.com, trenn@...e.de,
	prarit@...hat.com, tj@...nel.org, rusty@...tcorp.com.au,
	a.p.zijlstra@...llo.nl, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, suresh.b.siddha@...el.com,
	youquan.song@...el.com
Subject: [patch v2 0/4] MTRR rendezvous deadlock fix and cleanups using stop_machine()

Here is the v2 of the MTRR stop machine patchset.

First patch is a simple fix targeting 3.0 and the stable kernels.
This fixes the boot deadlock reported in the
https://bugzilla.novell.com/show_bug.cgi?id=672008

Second patch reorganizes the stop_cpus() code.

Third patch introduces stop_machine_from_inactive_cpu() so that we can do
stop machine from the cpu hotplug path, where the calling cpu is not
yet active.

Fourth patch uses the stop_machine() and stop_machine_from_inactive_cpu()
to implement the x86 MTRR rendezvous sequence and thus remove the duplicate
implementation of stop machine using stop_one_cpu_nowait().

changes from v1:
* update comments and use cpu active instead of the cpu online checks.

thanks,
suresh

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