linux-kernel - Re: A desktop environment[1] kernel wishlist

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: <1414420292.30379.55.camel@hadess.net>
Date:	Mon, 27 Oct 2014 15:31:32 +0100
From:	Bastien Nocera <hadess@...ess.net>
To:	Pavel Machek <pavel@....cz>
Cc:	John Stultz <john.stultz@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: A desktop environment[1] kernel wishlist

On Mon, 2014-10-27 at 10:28 +0100, Pavel Machek wrote:
> Hi!
> 
> > > I suspect wakeup type reporting is maybe not the best way to go about
> > > this, since there may be a number of causes for wakeups and they can
> > > arrive closely together in different orders, which can result in
> > > races.
> > > 
> > > For instance, if the machine suspends, and sets an alarm to be woken
> > > up at midnight to do a backup, if the user resumes their laptop at
> > > 11:59:59, should the backup still proceed at midnight?
> > 
> > No. And I would expect that we would get a wake up type of "power
> > button" or "lid open" in this case.
> 
> I believe you should really use "is lid opened or AC or dock
> connected" to determine if it was automatic resume or not. It should
> work better and you can actually do it today.

There's no LID or docks on a tablet.

> > >   For mobile
> > > devices this is an expected design point, but for off-the-shelf
> > > laptops with big fans and exhaust vents, I'm not sure how safe this
> > > would be, so you may need to constrain this functionality somehow (or
> > > look to see if a enforced low-power resume is possible).
> > 
> > I think that we won't know whether it's a problem until the point that
> > somebody actually implements it.
> 
> Kernel does not stop you at this point, right?
> 
> Suspend-to-partition is also doable today (see suspend.sf.net),

Is it perfect? Because no releases in 3 years kind of scares me.

>  or you
> can just swapon before starting. You can take it off the list, I
> believe.

Or we could create a new filesystem type that isn't swap, that isn't
used by swap at all, but could be created by distributions' installers.
Then I wouldn't need to hope that the swap didn't start being used in
between me enabling it, and the suspend actually occurring (making it
impossible to disable afterwards).

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