Please sign in to comment.
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 <email@example.com> Signed-off-by: Thomas Gleixner <firstname.lastname@example.org> Cc: "email@example.com" Cc: syzkaller <firstname.lastname@example.org> Cc: Al Viro <email@example.com> Cc: firstname.lastname@example.org Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701311521430.3457@nanos Signed-off-by: Thomas Gleixner <email@example.com>
- Loading branch information...