From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] blkdebug: Use QLIST_FOREACH_SAFE to resume IO
Date: Fri, 13 Dec 2013 17:13:01 +0100 [thread overview]
Message-ID: <20131213161301.GL3916@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1386919512-24520-1-git-send-email-famz@redhat.com>
Am 13.12.2013 um 08:25 hat Fam Zheng geschrieben:
> Qemu-iotest 030 was broken.
>
> When the coroutine runs and finishes, it will remove itself from the req
> list, so let's use safe version of foreach to avoid use after free.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
Thanks, applied to the block branch.
> diff --git a/block/blkdebug.c b/block/blkdebug.c
> index 37cf028..957be2c 100644
> --- a/block/blkdebug.c
> +++ b/block/blkdebug.c
> @@ -594,9 +594,9 @@ static int blkdebug_debug_breakpoint(BlockDriverState *bs, const char *event,
> static int blkdebug_debug_resume(BlockDriverState *bs, const char *tag)
> {
> BDRVBlkdebugState *s = bs->opaque;
> - BlkdebugSuspendedReq *r;
> + BlkdebugSuspendedReq *r, *next;
>
> - QLIST_FOREACH(r, &s->suspended_reqs, next) {
> + QLIST_FOREACH_SAFE(r, &s->suspended_reqs, next, next) {
> if (!strcmp(r->tag, tag)) {
> qemu_coroutine_enter(r->co, NULL);
> return 0;
This hunk wasn't strictly necessary because of the return 0, but it
doesn't hurt either.
Kevin
prev parent reply other threads:[~2013-12-13 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 7:25 [Qemu-devel] [PATCH] blkdebug: Use QLIST_FOREACH_SAFE to resume IO Fam Zheng
2013-12-13 16:13 ` Kevin Wolf [this message]
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=20131213161301.GL3916@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=famz@redhat.com \
--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).