Return-Path: Message-Id: <20130304033716.989555237@decadent.org.uk> Date: Mon, 04 Mar 2013 03:38:42 +0000 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: akpm@linux-foundation.org, Jan Kara , Christoph Hellwig , Jens Axboe , Jeff Moyer , Al Viro Subject: [ 095/153] fs: Fix possible use-after-free with AIO In-Reply-To: <20130304033707.648729212@decadent.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: 3.2-stable review patch. If anyone has any objections, please let me know. ------------------ From: Jan Kara commit 54c807e71d5ac59dee56c685f2b66e27cd54c475 upstream. Running AIO is pinning inode in memory using file reference. Once AIO is completed using aio_complete(), file reference is put and inode can be freed from memory. So we have to be sure that calling aio_complete() is the last thing we do with the inode. CC: Christoph Hellwig CC: Jens Axboe CC: Jeff Moyer Acked-by: Jeff Moyer Signed-off-by: Jan Kara Signed-off-by: Al Viro Signed-off-by: Ben Hutchings --- fs/direct-io.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/fs/direct-io.c +++ b/fs/direct-io.c @@ -304,9 +304,9 @@ static ssize_t dio_complete(struct dio * dio->end_io(dio->iocb, offset, transferred, dio->private, ret, is_async); } else { + inode_dio_done(dio->inode); if (is_async) aio_complete(dio->iocb, ret, 0); - inode_dio_done(dio->inode); } return ret;