diff options
| author | Thomas Gleixner <tglx@linutronix.de> | 2017-01-31 15:24:03 +0100 |
|---|---|---|
| committer | Sean McCreary <mccreary@mcwest.org> | 2017-08-07 18:11:00 -0600 |
| commit | 5a34ec804c3f9cb91ddff6c87e04595dd40929b5 (patch) | |
| tree | 35cb75b1bb7f98a03cd335009aa45c2cb845ef5d /lib/mpi/mpiutil.c | |
| parent | 78e667617712e4efde283bcb8dfee1a5bdbede06 (diff) | |
timerfd: Protect the might cancel mechanism proper
The handling of the might_cancel queueing is not properly protected, so
parallel operations on the file descriptor can race with each other and
lead to list corruptions or use after free.
Protect the context for these operations with a seperate lock.
The wait queue lock cannot be reused for this because that would create a
lock inversion scenario vs. the cancel lock. Replacing might_cancel with an
atomic (atomic_t or atomic bit) does not help either because it still can
race vs. the actual list operation.
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: "linux-fsdevel@vger.kernel.org"
Cc: syzkaller <syzkaller@googlegroups.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701311521430.3457@nanos
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Change-Id: I1f2d38a919ceb1ca1c7c9471dece0c1126383912
(cherry picked from commit 1e38da300e1e395a15048b0af1e5305bd91402f6)
Diffstat (limited to 'lib/mpi/mpiutil.c')
0 files changed, 0 insertions, 0 deletions