From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=47462 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OUf23-0004se-2n for qemu-devel@nongnu.org; Fri, 02 Jul 2010 08:07:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OUf22-00020s-21 for qemu-devel@nongnu.org; Fri, 02 Jul 2010 08:07:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51791) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OUf21-00020n-ON for qemu-devel@nongnu.org; Fri, 02 Jul 2010 08:07:46 -0400 From: Kevin Wolf Date: Fri, 2 Jul 2010 14:07:35 +0200 Message-Id: <1278072457-8156-1-git-send-email-kwolf@redhat.com> Subject: [Qemu-devel] [PATCH v2 0/2] block: Fix multiwrite error handling List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kwolf@redhat.com, stefanha@gmail.com The bdrv_aio_multiwrite error handling has some bugs that lead to premature cleanup, causing use-after-free and double free problems. v2: - Completely replaced patch 1 which Stefan found to be incorrect (thanks for the good review!). Hope I've got it right this time. Kevin Wolf (2): block: Fix early failure in multiwrite block: Handle multiwrite errors only when all requests have completed block.c | 40 ++++++++++++++++++++++++++++++---------- 1 files changed, 30 insertions(+), 10 deletions(-)