summaryrefslogtreecommitdiff
path: root/arch/arm/Kconfig-nommu
diff options
context:
space:
mode:
authorRoderick Colenbrander <roderick@gaikai.com>2019-08-03 01:50:19 +0300
committerJiri Kosina <jkosina@suse.cz>2019-08-06 13:46:15 +0300
commite0f6974a54d3f7f1b5fdf5a593bd43ce9206ec04 (patch)
tree2e217dec39f7f52d1cbfb53f883c683ce740f47c /arch/arm/Kconfig-nommu
parent6d4472d7bec39917b54e4e80245784ea5d60ce49 (diff)
downloadlinux-e0f6974a54d3f7f1b5fdf5a593bd43ce9206ec04.tar.xz
HID: sony: Fix race condition between rumble and device remove.
Valve reported a kernel crash on Ubuntu 18.04 when disconnecting a DS4 gamepad while rumble is enabled. This issue is reproducible with a frequency of 1 in 3 times in the game Borderlands 2 when using an automatic weapon, which triggers many rumble operations. We found the issue to be a race condition between sony_remove and the final device destruction by the HID / input system. The problem was that sony_remove didn't clean some of its work_item state in "struct sony_sc". After sony_remove work, the corresponding evdev node was around for sufficient time for applications to still queue rumble work after "sony_remove". On pre-4.19 kernels the race condition caused a kernel crash due to a NULL-pointer dereference as "sc->output_report_dmabuf" got freed during sony_remove. On newer kernels this crash doesn't happen due the buffer now being allocated using devm_kzalloc. However we can still queue work, while the driver is an undefined state. This patch fixes the described problem, by guarding the work_item "state_worker" with an initialized variable, which we are setting back to 0 on cleanup. Signed-off-by: Roderick Colenbrander <roderick.colenbrander@sony.com> CC: stable@vger.kernel.org Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'arch/arm/Kconfig-nommu')
0 files changed, 0 insertions, 0 deletions