diff options
author | Lan Tianyu <tianyu.lan@intel.com> | 2014-08-26 01:29:24 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-09-17 09:19:19 -0700 |
commit | 4b56ddf9debed7505e336202209a8a2dfda5852d (patch) | |
tree | 9a43c151a57256084c7f5e2b3be23d16867cf427 /include | |
parent | e6b21fd09d5c83adf6911a856345ebf6de15d321 (diff) | |
download | linux-stable-4b56ddf9debed7505e336202209a8a2dfda5852d.tar.gz linux-stable-4b56ddf9debed7505e336202209a8a2dfda5852d.tar.bz2 linux-stable-4b56ddf9debed7505e336202209a8a2dfda5852d.zip |
ACPI: Run fixed event device notifications in process context
commit 236105db632c6279a020f78c83e22eaef746006b upstream.
Currently, notify callbacks for fixed button events are run from
interrupt context. That is not necessary and after commit 0bf6368ee8f2
(ACPI / button: Add ACPI Button event via netlink routine) it causes
netlink routines to be called from interrupt context which is not
correct.
Also, that is different from non-fixed device events (including
non-fixed button events) whose notify callbacks are all executed from
process context.
For the above reasons, make fixed button device notify callbacks run
in process context which will avoid the deadlock when using netlink
to report button events to user space.
Fixes: 0bf6368ee8f2 (ACPI / button: Add ACPI Button event via netlink routine)
Link: https://lkml.org/lkml/2014/8/21/606
Reported-by: Benjamin Block <bebl@mageta.org>
Reported-by: Knut Petersen <Knut_Petersen@t-online.de>
Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
[rjw: Function names, subject and changelog.]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions