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] [day] [month] [year] [list]
Date:	Sun, 15 Feb 2009 00:02:21 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Jiri Slaby <jirislaby@...il.com>, lenb@...nel.org,
	mingo@...hat.com, linux-kernel@...r.kernel.org,
	Pavel Machek <pavel@...e.cz>
Subject: Re: [PATCH 1/1] x86_64: fix s3 fail path


* Rafael J. Wysocki <rjw@...k.pl> wrote:

> On Saturday 14 February 2009, Jiri Slaby wrote:
> > Rafael J. Wysocki napsal(a):
> > > On Monday 09 February 2009, Jiri Slaby wrote:
> > >> As acpi_enter_sleep_state can fail, take this into account in
> > >> do_suspend_lowlevel and don't return to the do_suspend_lowlevel's
> > >> caller. This would break (currently) fpu status and preempt count.
> > >>
> > >> Technically, this means use `call' instead of `jmp' and `jmp' to
> > >> the `resume_point' after the `call' (i.e. if
> > >> acpi_enter_sleep_state returns=fails). `resume_point' will handle
> > >> the restore of fpu and preempt count gracefully.
> > >>
> > >> Signed-off-by: Jiri Slaby <jirislaby@...il.com>
> > >> Cc: Len Brown <lenb@...nel.org>
> > >> Cc: Pavel Machek <pavel@...e.cz>
> > >> Cc: Rafael J. Wysocki <rjw@...k.pl>
> > > 
> > > What kernel is this patch against?  It doesn't apply to the mainline.
> > 
> > It is applicable even after
> > [PATCH v2 1/1] x86_64: acpi/wakeup_64 cleanup
> > from
> > http://lkml.org/lkml/2009/2/7/101
> > which is not present anywhere so far.
> 
> Thanks, I'm going to push both patches through Len, if Ingo doesn't mind.

Fine with me.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ