linux-kernel - Re: [PATCH 0/6] [RFC] Proposal for optimistic suspend idea.

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]

Date:	Wed, 28 Sep 2011 02:09:17 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	John Stultz <john.stultz@...aro.org>
cc:	Peter Zijlstra <peterz@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, arve@...roid.com,
	markgross@...gnar.org, Alan Stern <stern@...land.harvard.edu>,
	amit.kucheria@...aro.org, farrowg@...ibm.com,
	"Dmitry Fink (Palm GBU)" <Dmitry.Fink@...m.com>,
	linux-pm@...ts.linux-foundation.org, khilman@...com,
	Magnus Damm <damm@...nsource.se>, mjg@...hat.com
Subject: Re: [PATCH 0/6] [RFC] Proposal for optimistic suspend idea.

On Mon, 26 Sep 2011, John Stultz wrote:
> Another use case I've heard about are systems that have firmware updates

Yes, I have heard about people wanting O_PONIES ...

> that are remotely triggered. Should the system go into suspend while the
> firmware update is going on, you end up with a brick.

If someone came up with a firmware update mechanism which is not
coping with unexpected interruption of any kind, then wakelocks are
not making any difference.

Please collect the resulting bricks and shove them back to those who
thought that remote firmware updates do not have to be engineered and
the resulting fallout can be blamed on the kernel.

We have proper mechanisms in place to handle such stuff, but they need
proper overall design and definitely a bit more brain usage than just
yelling "wakelock".

Thanks,

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