From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: next-20130117 - kernel BUG with aio Date: Thu, 24 Jan 2013 13:27:59 -0800 Message-ID: <20130124132759.c892fb4c.akpm@linux-foundation.org> References: <3544.1358774694@turing-police.cc.vt.edu> <2553.1358890098@turing-police.cc.vt.edu> <13450.1359048141@turing-police.cc.vt.edu> <20130124211850.GH26407@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Valdis.Kletnieks@vt.edu, Hillf Danton , Benjamin LaHaise , linux-kernel@vger.kernel.org, linux-aio@kvack.org, zab@zabbo.net, linux-fsdevel@vger.kernel.org To: Kent Overstreet Return-path: In-Reply-To: <20130124211850.GH26407@google.com> Sender: owner-linux-aio@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 24 Jan 2013 13:18:50 -0800 Kent Overstreet wrote: > So, Andrew - that "smoosh struct kiocb" patch should just be dropped, > even if I fixed that issue clearly the idea is a lot less safe than I > thought. I've got patches for the other stuff I'm going to mail out > momentarily. Dropped. Do you expect that this will fix everything? Please cc linux-fsdevel on the aio stuff - I'm seeing some AIO things over there which aren't cc'ed to lkml or linux-aio. Please also take a look at Jan's recent http://www.spinics.net/lists/linux-fsdevel/msg61738.html and have a think about how this plays with your patchset. -- 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