linux-kernel - Re: [PATCH] x86_64 kexec: Remove experimental mark of kexec

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]

Message-ID: <m1odtsrz6e.fsf@ebiederm.dsl.xmission.com>
Date:	Thu, 07 Sep 2006 00:03:21 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	piet@...elane.com
Cc:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org, fastboot@...l.org
Subject: Re: [PATCH] x86_64 kexec: Remove experimental mark of kexec

Piet Delaney <piet@...elane.com> writes:

> On Wed, 2006-09-06 at 21:22 +0200, Andi Kleen wrote:
>> On Wednesday 06 September 2006 18:55, Eric W. Biederman wrote:
>> > 
>> > kexec has been marked experimental for a year now and all
>> > of the serious problems have been worked through.  So it
>> > is time (if not past time) to remove the experimental mark.
>> > 
>> 
>> Hmm, I personally have some doubts it is really not experimental
>> (not because of the kexec code itself, but because of all the other drivers
>> that still break)
>
> What drivers does kexec break?

Kexec doesn't break any drivers.  kexec exposes bugs in driver initialization
handling, when drivers on not robust.

The normal kexec case should be quite simple to handle and because we cleanup
just like a reboot, the difference is that we don't ask the BIOS to reset us
first.

The kexec on panic case is painful, because drivers in the original kernel are
not stopped or shutdown, and so the secondary kernel gets to initialize drivers
from an essentially random state.

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