linux-kernel - Re: Hibernation Redesign

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: <200707091709.09912.oliver@neukum.org>
Date:	Mon, 9 Jul 2007 17:09:09 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	Jeremy Maitin-Shepard <jbms@....edu>
Cc:	Pavel Machek <pavel@....cz>, Nick Piggin <nickpiggin@...oo.com.au>,
	Al Boldi <a1426z@...ab.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Hibernation Redesign

Am Montag, 9. Juli 2007 schrieb Jeremy Maitin-Shepard:
> Oliver Neukum <oliver@...kum.org> writes:
> 
> [snip]
> 
> > Hm, once the new kernel is booted, this decision is irrevocable, isn't it?
> > Is there any way to deal with errors by handing control back?
> 
> Returning to the old kernel can be done by telling drivers to set the
> hardware to the appropriate state, then copying the backed up memory
> back to the beginning of physical memory, and finally jumping to the old
> kernel.  It would be much like what is done to resume from hibernation.

If you can do that, why load a new kernel image?

	Regards
		Oliver

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