linux-kernel - Re: Attempted summary of suspend-blockers LKML thread

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=yqnOdsJvq8dYmCjS6Ja758d9y+CUAHG069Mmd@mail.gmail.com>
Date:	Thu, 12 Aug 2010 03:23:44 +0300
From:	Felipe Contreras <felipe.contreras@...il.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>, "Ted Ts'o" <tytso@....edu>,
	"david@...g.hm" <david@...g.hm>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Brian Swetland <swetland@...gle.com>,
	kevin granade <kevin.granade@...il.com>,
	"Arve Hj?nnev?g" <arve@...roid.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Arjan van de Ven <arjan@...radead.org>,
	"linux-pm@...ts.linux-foundation.org" 
	<linux-pm@...ts.linux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"pavel@....cz" <pavel@....cz>,
	"florian@...kler.org" <florian@...kler.org>,
	"stern@...land.harvard.edu" <stern@...land.harvard.edu>,
	"peterz@...radead.org" <peterz@...radead.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"alan@...rguk.ukuu.org.uk" <alan@...rguk.ukuu.org.uk>
Subject: Re: Attempted summary of suspend-blockers LKML thread

On Sun, Aug 8, 2010 at 9:34 PM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On 8 Aug 2010, at 18:08, Felipe Contreras <felipe.contreras@...il.com> wrote:
>
>> On Sun, Aug 8, 2010 at 7:08 PM, Matthew Garrett <mjg59@...f.ucam.org> wrote:
>>> It's clearly possible for a pathological Android application to destroy
>>> the power management policy. But to do that, the author would have to
>>> explicitly take a wakelock. That's difficult to do by accident.
>>
>> The writer can take a wakelock the whole time the application is
>> running (isn't that the typical case?), because perhaps the author
>> realizes that way the application works correctly, or he copy-pasted
>> it from somewhere else.
>
> That would be exceptionally unusual. A more common case is that the application will take a wakelock while performing some specific long running task which needs no user intervention such as downloading a file or displaying constantly update status that the user is not expected to respond to. There's no need for applications to take wakelocks while the user is directly interacting with them since the system will be kept awake as a result of the user interaction, the wakelocks are used to override the default suspend that occurs when the user is not interacting with the device.

Fair enough, but if that the case, if suspend blockers are to be used
in desktop software, everything would need extensive modifications
just to work. I remember somebody said that was not the case, I
thought it was because the lock could be held the whole time the
application is running.

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