From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: Clean up after deleting BHs
Date: Tue, 23 Jun 2009 21:31:55 +0300 [thread overview]
Message-ID: <4A411F9B.5020508@redhat.com> (raw)
In-Reply-To: <20090623182622.GA5804@lst.de>
On 06/23/2009 09:26 PM, Christoph Hellwig wrote:
> On Tue, Jun 23, 2009 at 07:57:01PM +0300, Avi Kivity wrote:
>
>>> I think not having the state of the private acb area cleared over a
>>> free/realloc cycle is pretty dangerous. Wouldn't it be better to always
>>> clear that space in qemu_aio_get?
>>>
>>>
>> Maybe, but that's a bigger change. Let's start with this (in stable-
>> too) and rework aio later.
>>
>
> It's actually smaller - half the size to be exact :)
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
>
> Index: qemu/block.c
> ===================================================================
> --- qemu.orig/block.c 2009-06-23 20:16:48.283930485 +0200
> +++ qemu/block.c 2009-06-23 20:16:57.158834441 +0200
> @@ -1515,6 +1515,7 @@ void *qemu_aio_get(AIOPool *pool, BlockD
> acb->bs = bs;
> acb->cb = cb;
> acb->opaque = opaque;
> + memset(acb + 1, 0, pool->aiocb_size - sizeof(BlockDriverAIOCB));
> return acb;
> }
>
I meant in an omg we have to look at all the consequences way rather
than byte count. This patch is somewhat less local.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-06-23 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 13:20 [Qemu-devel] [PATCH] block: Clean up after deleting BHs Avi Kivity
2009-06-23 13:37 ` Filip Navara
2009-06-23 16:50 ` Christoph Hellwig
2009-06-23 16:57 ` Avi Kivity
2009-06-23 18:08 ` Filip Navara
2009-06-23 18:11 ` Avi Kivity
2009-06-23 18:26 ` Christoph Hellwig
2009-06-23 18:31 ` Avi Kivity [this message]
2009-06-23 19:41 ` Christoph Hellwig
2009-06-23 19:50 ` Avi Kivity
2009-06-23 20:21 ` Filip Navara
2009-06-24 18:31 ` Stefan Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A411F9B.5020508@redhat.com \
--to=avi@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).