From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>,
pbonzini@redhat.com, Julia Suvorova <jusual@mail.ru>,
Aarushi Mehta <mehta.aaru20@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] block/linux-aio: explictly clear laiocb->co
Date: Thu, 30 May 2019 10:42:14 +0200 [thread overview]
Message-ID: <20190530084214.GA4890@linux.fritz.box> (raw)
In-Reply-To: <20190527092319.15844-1-stefanha@redhat.com>
Am 27.05.2019 um 11:23 hat Stefan Hajnoczi geschrieben:
> qemu_aio_get() does not zero allocated memory. Explicitly initialize
> laiocb->co to prevent an uninitialized memory access in
> qemu_laio_process_completion().
>
> Note that this bug has never manifested itself. I guess we're lucky!
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
That the bug never manifested itself might be because it's in an unused
function. How about we finally just remove the unused callback-based
laio_submit() from the code?
At the time when I converted linux-aio to coroutines, someone (maybe
Paolo?) insisted that we keep the old interface because we might add a
new user sometime with possible shortcuts that bypass the whole coroutine
path, but it hasn't happened and I think we've moved even further in the
opposite direction since then.
Kevin
> I challenge you to find a place where laiocb->co is initialized and then
> we can drop this patch. I've double-checked and cannot find it...
>
> block/linux-aio.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/block/linux-aio.c b/block/linux-aio.c
> index d4b61fb251..a097653be6 100644
> --- a/block/linux-aio.c
> +++ b/block/linux-aio.c
> @@ -440,6 +440,7 @@ BlockAIOCB *laio_submit(BlockDriverState *bs, LinuxAioState *s, int fd,
> int ret;
>
> laiocb = qemu_aio_get(&laio_aiocb_info, bs, cb, opaque);
> + laiocb->co = NULL;
> laiocb->nbytes = nb_sectors * BDRV_SECTOR_SIZE;
> laiocb->ctx = s;
> laiocb->ret = -EINPROGRESS;
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-05-30 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 9:23 [Qemu-devel] [PATCH] block/linux-aio: explictly clear laiocb->co Stefan Hajnoczi
2019-05-30 8:42 ` Kevin Wolf [this message]
2019-05-30 14:07 ` Paolo Bonzini
2019-05-30 17:39 ` Julia Suvorova via Qemu-devel
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=20190530084214.GA4890@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=jusual@mail.ru \
--cc=mehta.aaru20@gmail.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).