From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mateusz Guzik Subject: Re: [PATCH] aio: fix potential leak in aio_run_iocb(). Date: Thu, 1 May 2014 08:24:06 +0200 Message-ID: <20140501062406.GB1806@mguzik.redhat.com> References: <1398915088-8472-1-git-send-email-chianglungyu@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Benjamin LaHaise , Alexander Viro , linux-aio@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Leon Yu Return-path: Content-Disposition: inline In-Reply-To: <1398915088-8472-1-git-send-email-chianglungyu@gmail.com> Sender: owner-linux-aio@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Thu, May 01, 2014 at 03:31:28AM +0000, Leon Yu wrote: > iovec should be reclaimed whenever caller of rw_copy_check_uvector() returns, > but it doesn't hold when failure happens right after aio_setup_vectored_rw(). > There is a proposal (wich a patch) to modify semantics of rw_copy_check_uvector so that it frees stuff on error, taking care of this case as well: https://lkml.org/lkml/2014/4/25/778 -- Mateusz Guzik -- 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