linux-kernel - Re: Generic events for wake up from S1-S4

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: <20090718235609.GC25343@khazad-dum.debian.net>
Date:	Sat, 18 Jul 2009 20:56:10 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
	linux-kernel@...r.kernel.org,
	Johannes Berg <johannes@...solutions.net>,
	"John W. Linville" <linville@...driver.com>,
	Jouni Malinen <j@...fi>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Stephen Chen <Stephen.Chen@...eros.com>
Subject: Re: Generic events for wake up from S1-S4

On Sat, 18 Jul 2009, Luis R. Rodriguez wrote:
> Hm yeah, but I doubt someone will do that, generally we'd get one wake
> up event. Can't we just report the first one and ignore the rest?

Well, I'd say keeping it simple is best, here.  What if you ignore the more
interesting wakeup events by chance (and it is really up to userspace to
know what it considers interesting...)?  IMHO, just issue as many
notifications as needed, let userspace filter it if it wants.

But if you guys are talking about something really generic, shouldn't it
also provide the important "why" along with the "who"?

Even for the most common cases, the "why" is useful: userspace may well want
to run special routines when it wakes up because of WoL and WoW (instead of
a key press, lid open or mouse movement...).

When you factor in wakeups caused by platform alarms, well, the "why"
becomes even more interesting.

> > What about simply reporting "wake event happened on this device" and
> > doing that for all the devices?
> 
> That's fine too. Just think it would be nice to be more specific if possible.

A generic way for a device (of any sort, not just network devices!) to
report that they just issued a system wakeup message, as well as the reason
it did that seems like a good way to do it to me.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/