On Mon, May 17, 2010 at 12:50:40PM -0700, Daniel Walker wrote:
> On Mon, 2010-05-17 at 20:34 +0100, Matthew Garrett wrote:
>
> > int main() {
> > int i;
> > while (1)
> > i++;
> > return 0;
> > }
> >
>
> We already know it's really rare on an embedded system you would get
> this bad of an app. However, if you assume that you might have this 1 in
> a million app, couldn't we just have a watch dog that identifies and
> kills it. It would also let the user know what happened of course.
> Killing the app seems pretty reasonable to me.
In a world where anyone can provide this kind of app for Android users,
I'd submit that it's going to be significantly more common than that.
I'd expect real world cases to be at least slightly more subtle, but...
But yeah. Fundamentally the real argument here isn't about suspend
blockers. It's about whether it's valid to require that the Linux kernel
provide mechanisms to enable power management in the face of poorly
written applications. If you think that that argument is invalid then
suspend blockers are an entirely unnecessary set of layering violations.
If you think it's valid, suspend blockers are the only currently
proposed solution that will work in a race-free manner.
--
Matthew Garrett | mjg59@xxxxxxxxxxxxx
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm
