From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin LaHaise Subject: Re: [PATCH] aio: clean up aio ring in the fail path Date: Fri, 6 Dec 2013 10:36:03 -0500 Message-ID: <20131206153603.GE13581@kvack.org> References: <529F019A.2040401@cn.fujitsu.com> <20131206152654.GD13581@kvack.org> <20131206153413.GA31613@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Dave Jones , Gu Zheng , linux-aio@kvack.org, fsdevel , linux-kernel , Al Viro , Kent , Kristian Nielsen Return-path: Content-Disposition: inline In-Reply-To: <20131206153413.GA31613@redhat.com> Sender: owner-linux-aio@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Dec 06, 2013 at 10:34:13AM -0500, Dave Jones wrote: > On Fri, Dec 06, 2013 at 10:26:54AM -0500, Benjamin LaHaise wrote: > > On Wed, Dec 04, 2013 at 06:19:06PM +0800, Gu Zheng wrote: > > > Clean up the aio ring file in the fail path of aio_setup_ring > > > and ioctx_alloc. And maybe it can fix the GPF issue reported by > > > Dave Jones: > > > https://lkml.org/lkml/2013/11/25/898 > > > > Good catch. I've applied this to my aio-next tree. It does indeed look > > like it could be the cause of Dave's GPF -- I'll try to trigger it with > > some other kernel debug options on and see if the EAGAIN failure case can > > trip it up. > > I think I forgot to reply and let you know this seems to fix it for me. Excellent! I'll send this out and get it queued up for -stable as well. -ben > Dave -- "Thought is the essence of where you are now." -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to majordomo@kvack.org. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: aart@kvack.org