summaryrefslogtreecommitdiff
path: root/tools/perf/util/llvm-utils.c
diff options
context:
space:
mode:
authorDavid Frey <dpfrey@gmail.com>2019-09-20 01:54:18 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-10-17 23:43:40 +0300
commit18bb45dfeb87164bbaf0246311ab25f3289058ed (patch)
tree01232051095e3bb2d105a6ac134a6d493d3e7288 /tools/perf/util/llvm-utils.c
parent9dddc22201f62e7778ac0e1d28fba4eb2ff29a68 (diff)
downloadlinux-18bb45dfeb87164bbaf0246311ab25f3289058ed.tar.xz
iio: light: opt3001: fix mutex unlock race
commit 82f3015635249a8c8c45bac303fd84905066f04f upstream. When an end-of-conversion interrupt is received after performing a single-shot reading of the light sensor, the driver was waking up the result ready queue before checking opt->ok_to_ignore_lock to determine if it should unlock the mutex. The problem occurred in the case where the other thread woke up and changed the value of opt->ok_to_ignore_lock to false prior to the interrupt thread performing its read of the variable. In this case, the mutex would be unlocked twice. Signed-off-by: David Frey <dpfrey@gmail.com> Reviewed-by: Andreas Dannenberg <dannenberg@ti.com> Fixes: 94a9b7b1809f ("iio: light: add support for TI's opt3001 light sensor") Cc: <Stable@vger.kernel.org> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/util/llvm-utils.c')
0 files changed, 0 insertions, 0 deletions