From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f173.google.com (mail-vc0-f173.google.com [209.85.220.173]) by kanga.kvack.org (Postfix) with ESMTP id 6E9866B0035 for ; Fri, 28 Mar 2014 13:08:49 -0400 (EDT) Received: by mail-vc0-f173.google.com with SMTP id il7so6083347vcb.18 for ; Fri, 28 Mar 2014 10:08:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20140328145826.GE29656@kvack.org> References: <20140327134653.GA22407@kvack.org> <20140327200851.GL17679@kvack.org> <20140327205749.GM17679@kvack.org> <20140328145826.GE29656@kvack.org> Date: Fri, 28 Mar 2014 10:08:47 -0700 Message-ID: Subject: Re: git pull -- [PATCH] aio: v2 ensure access to ctx->ring_pages is correctly serialised From: Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: Benjamin LaHaise Cc: Yasuaki Ishimatsu , Sasha Levin , Tang Chen , Gu Zheng , Linux Kernel Mailing List , stable , linux-aio@kvack.org, linux-mm On Fri, Mar 28, 2014 at 7:58 AM, Benjamin LaHaise wrote: > > Here's a respin of that part. I just moved the mutex initialization up so > that it's always valid in the err path. I have also run this version of > the patch through xfstests and my migration test programs and it looks > okay. Ok. I can't find any issues with this version. How critical is this? Should I take it now, or with more testing during the 3.15 merge window and then just have it picked up from stable? Do people actually trigger the bug in real life, or has this been more of a trinity/source code analysis thing? Linus -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org