linux-kernel - [GIT PULL] (xen) stable/for-linus-3.7-rc7-tag

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>] [day] [month] [year] [list]

Message-ID: <20120924134343.GA31618@phenom.dumpdata.com>
Date:	Mon, 24 Sep 2012 09:43:43 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Cc:	xen-devel@...ts.xensource.com
Subject: [GIT PULL] (xen) stable/for-linus-3.7-rc7-tag

Hey Linus,

I've one fix for which I got the Tested-by right after I sent you a git pull on
Friday. If you have some extra patches for rc7, please consider pulling it.
If you don't have any - I will just stick this in my for-v3.7.

git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.6-rc7-tag

It is a bug-fix when we run the initial PV guest on a AMD K8 machine
and have CONFIG_AMD_NUMA enabled and detect the NUMA topology from the Northbridge.

We end up in the situation where the initial domain gets too much information
and gets confused and crashes - the fix is to restrict the domain to get the
information - and we do it by just disabling NUMA on the PV guest (the hypervisor is
still able to do its proper NUMA allocations of guests). It is OK to disable the PV
guest from accessing NUMA data as right now we do not inject any NUMA node information
to the PV guests. When we do get to that point, then this patch will have to be reverted.

Konrad Rzeszutek Wilk (1):
      xen/boot: Disable NUMA for PV guests.

 arch/x86/xen/setup.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
--
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/