linux-kernel - Re: [linux-pm] [PATCH -mm] kexec jump -v9

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: <20080322162110.GA32058@atrey.karlin.mff.cuni.cz>
Date:	Sat, 22 Mar 2008 17:21:10 +0100
From:	Pavel Machek <pavel@....cz>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	nigel@...el.suspend2.net,
	Kexec Mailing List <kexec@...ts.infradead.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-pm@...ts.linux-foundation.org,
	Vivek Goyal <vgoyal@...hat.com>,
	Len Brown <len.brown@...el.com>
Subject: Re: [linux-pm] [PATCH -mm] kexec jump -v9

> On Fri, 21 Mar 2008, Rafael J. Wysocki wrote:
> 
> > > > > Well, in fact ACPI has something called the NVS memory, which we're supposed
> > > > > to restore during the resume and which we're not doing.  The problem may be
> > > > > related to this.
> > > > 
> > > > No, it can't be.  ACPI won't expect the NVS memory to be restored 
> > > > following an S5-shutdown.  In fact, as far as ACPI is concerned, 
> > > > resuming from an S5-type hibernation should not be considered a resume 
> > > > at all but just an ordinary reboot.
> > 
> > I agree here.
> > 
> > > > All ACPI-related memory areas in the boot kernel should be passed directly
> > > > through to the image kernel.
> > 
> > However, the image kernel is supposed to restore the NVS area (from the
> > image) before executing _WAK.
> 
> It's supposed to do that when resuming from an S4 hibernation, not 
> when resuming from an S5 hibernation.
> 
> > > How can we pass interpretter state? I do not think we do this kind of
> > > passing.
> > 
> > The interpreter state is passed withing the image.  The platform state is not.
> 
> For an S5 hibernation, the interpreter state within the image is wrong.  
> The image kernel needs to have the interpreter state from the boot 
> kernel -- I don't know if this is possible.

yes, nosave pages could be used to do this passing -- if we can put
interpretter state into pre-allocated memory block.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/