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  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]
Date:	Mon, 24 May 2010 23:24:51 +0200
From:	Pavel Machek <>
To:	Alan Stern <>
Cc:	Paul Walmsley <>, Arve Hj?nnev?g <>,
	Linux-pm mailing list <>,
	Kernel development list <>,
	Tejun Heo <>, Oleg Nesterov <>,
	Tony Lindgren <>,
	Kevin Hilman <>,, Theodore Ts'o <>,
	mark gross <>,
	Arjan van de Ven <>,
	Geoff Smith <>,
	Brian Swetland <>,
	"Rafael J. Wysocki" <>,
	Matthew Garrett <>,
	Beno?t Cousson <>,,
	Vitaly Wool <>,
	Linus Walleij <>,
	Mark Brown <>,
	Liam Girdwood <>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6)


> > There are several general problems with the design of opportunistic
> > suspend and suspend-blocks.
> > 
> > 1. The opportunistic suspend code bypasses existing Linux kernel code,
> >    such as timers and the scheduler, that indicates when code
> >    needs to run, and when the system is idle.
> Whoa!  That's not my understanding at all.
> As I see it, opportunistic suspend doesn't bypass any code that isn't 
> already bypassed by the existing suspend code.  Users can do
> 	echo mem >/sys/power/state
> whenever they want, without regard to kernel timers and the scheduler 
> (other than the fact that the user's thread must be running in order to 
> carry out the write, of course).

Yep. And while I'm co-responsible for that interface, I would not
call it exactly nice. Yes, it does the job.

But imagine horrors atd/cron would have to do to work properly with
that interface... setting rtc wakeups etc.

So yes, mem > state already breaks promises, but lets not extend that.

(cesky, pictures)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists