linux-kernel - Re: [PATCH 00/14] x86: disable virt on kdump and emergency

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

Message-ID: <4912BDC5.3000508@redhat.com>
Date:	Thu, 06 Nov 2008 11:49:57 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Eduardo Habkost <ehabkost@...hat.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Simon Horman <horms@...ge.net.au>,
	Andrew Morton <akpm@...l.org>, Vivek Goyal <vgoyal@...hat.com>,
	Haren Myneni <hbabu@...ibm.com>,
	Andrey Borzenkov <arvidjaar@...l.ru>, mingo@...hat.com,
	"Rafael J. Wysocki" <rjw@...k.pl>, kexec@...ts.infradead.org,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/14] x86: disable virt on kdump and emergency_restart

Ingo Molnar wrote:
> general ack for the x86 bits, but i'm not sure whether we should be 
> pushing this upstream so late in the cycle. If we do it in the next 
> cycle then it's best we do it in the x86 tree, the KVM impact seems 
> much smaller than the general x86 impact.
>   

It certainly doesn't fall under the recent regression rule, and there's 
a simple workaround (rmmod -r kvm) so I agree it's best to defer for the 
next cycle.

-- 
error compiling committee.c: too many arguments to function

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