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
| ||
|
Date: Wed, 10 Jun 2020 16:01:45 +0200 From: "Rafael J. Wysocki" <rafael@...nel.org> To: Hans de Goede <hdegoede@...hat.com> Cc: Andrzej Pietrasiewicz <andrzej.p@...labora.com>, "Rafael J. Wysocki" <rafael@...nel.org>, Linux PM <linux-pm@...r.kernel.org>, ACPI Devel Maling List <linux-acpi@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-iio@...r.kernel.org, Linux ARM <linux-arm-kernel@...ts.infradead.org>, Linux Samsung SoC <linux-samsung-soc@...r.kernel.org>, linux-input@...r.kernel.org, linux-tegra <linux-tegra@...r.kernel.org>, patches@...nsource.cirrus.com, ibm-acpi-devel@...ts.sourceforge.net, Platform Driver <platform-driver-x86@...r.kernel.org>, "Rafael J . Wysocki" <rjw@...ysocki.net>, Len Brown <lenb@...nel.org>, Jonathan Cameron <jic23@...nel.org>, Hartmut Knaack <knaack.h@....de>, Lars-Peter Clausen <lars@...afoo.de>, Peter Meerwald-Stadler <pmeerw@...erw.net>, Kukjin Kim <kgene@...nel.org>, Krzysztof Kozlowski <krzk@...nel.org>, Dmitry Torokhov <dmitry.torokhov@...il.com>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>, Fabio Estevam <festevam@...il.com>, NXP Linux Team <linux-imx@....com>, Vladimir Zapolskiy <vz@...ia.com>, Sylvain Lemieux <slemieux.tyco@...il.com>, Laxman Dewangan <ldewangan@...dia.com>, Thierry Reding <thierry.reding@...il.com>, Jonathan Hunter <jonathanh@...dia.com>, Barry Song <baohua@...nel.org>, Michael Hennerich <michael.hennerich@...log.com>, Nick Dyer <nick@...anahar.org>, Ferruh Yigit <fery@...ress.com>, Sangwon Jee <jeesw@...fas.com>, Peter Hutterer <peter.hutterer@...hat.com>, Henrique de Moraes Holschuh <ibm-acpi@....eng.br>, Collabora Kernel ML <kernel@...labora.com> Subject: Re: [PATCH v4 0/7] Support inhibiting input devices On Wed, Jun 10, 2020 at 3:21 PM Hans de Goede <hdegoede@...hat.com> wrote: > > Hi, > > On 6/10/20 3:12 PM, Andrzej Pietrasiewicz wrote: > > Hi All, > > [cut] > > What would it mean to become a wakeup source if there are no users, > > or nobody has ever opened the device? There are no interested > > input handlers (users) so what's the point of becoming a wakeup > > source? Why would the system need to wake up? > > Well this is what we have been doing so far, so arguably we > need to keep doing it to avoid regressions / breaking our ABI. > > Lets for example take a laptop, where when suspended the > power-button is the only valid wakeup-source and this is > running good old slackware with fvwm2 or windowmaker as > "desktop environment", then likely no process will have > the power-button input evdev node open. Still we should > wakeup the laptop on the power-button press, otherwise > it will never wakeup. > > Note I agree with you that the way this works is not > ideal, I just do not think that we can change it. Please note that "no users" merely means that user space is not interested in receiving and processing the events from that device. If it is configured for system wakeup, it doesn't matter whether or not user space will consume the related events. Thanks!
Powered by blists - more mailing lists