linux-kernel - RE: [PATCH 6/6] x86-mce: ensure the MCP timer is not already set in the mce_timer

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:	Wed, 9 Jul 2014 21:04:06 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Havard Skinnemoen <hskinnemoen@...gle.com>,
	Borislav Petkov <bp@...en8.de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Ewout van Bekkum" <ewout@...gle.com>
Subject: RE: [PATCH 6/6] x86-mce: ensure the MCP timer is not already set in
 the mce_timer_fn.

+	/* Ensure a CMCI interrupt can't preempt this. */
+	local_irq_save(flags);
 	if (mce_available(__this_cpu_ptr(&cpu_info))) {
 		machine_check_poll(MCP_TIMESTAMP,
 				&__get_cpu_var(mce_poll_banks));

Does this remove the problem that you fixed in part4?  If a CMCI can
no longer interrupt a poll ... do we really need the locks you added?

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