From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751959AbdAaLpR (ORCPT ); Tue, 31 Jan 2017 06:45:17 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:34232 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750945AbdAaLpK (ORCPT ); Tue, 31 Jan 2017 06:45:10 -0500 Date: Tue, 31 Jan 2017 12:45:07 +0100 (CET) From: Thomas Gleixner To: Dmitry Vyukov cc: Al Viro , "linux-fsdevel@vger.kernel.org" , LKML , syzkaller Subject: Re: timerfd: use-after-free in timerfd_remove_cancel In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 31 Jan 2017, Thomas Gleixner wrote: > On Mon, 30 Jan 2017, Dmitry Vyukov wrote: > > > > Seems that ctx->might_cancel is racy. > > Yes, it is. Fix below. And the fix is racy as well. Darn, we really need to lock the context to avoid that mess.