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-next>] [day] [month] [year] [list]
Message-Id: <1280940316-7966-1-git-send-email-bp@amd64.org>
Date:	Wed,  4 Aug 2010 18:45:14 +0200
From:	Borislav Petkov <bp@...64.org>
To:	<hpa@...or.com>, <mingo@...e.hu>, <tglx@...utronix.de>
Cc:	<andreas.herrmann3@....com>, conny.seidel@....com,
	<joerg.roedel@....com>, Bhavna.Sarathy@....com, <greg@...ah.com>,
	<x86@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] Fix 32-bit CPU hotplug issue on AMD

From: Borislav Petkov <borislav.petkov@....com>

Hi,

the following two patches fix an issue which one of our tests triggers
here on a 32-bit kernel while exercising the CPU hotplug path. More
details are to be found in the respective commit messages.

Now, considering the seriousness of the issue, I'd very much like
to backport the fixes to .32 and .34. And while the fixes are not
oneliners, they're straightforward enough to not cause any problems
IMHO. But I may be biased from staring at them for a while now so what
do you guys, think, any objections to backporting those?

Thanks.
--
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