qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, Arun R Bharadwaj <arun@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/6] Move paio_cancel() to new infrastructure.
Date: Tue, 30 Nov 2010 15:20:33 -0800	[thread overview]
Message-ID: <4CF586C1.4070405@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTi=5td01Qw_a0pXE15=jH7m+7obCfH-jVKnx28y1@mail.gmail.com>

On 11/19/2010 2:07 AM, Stefan Hajnoczi wrote:
> On Thu, Nov 18, 2010 at 6:06 PM, Arun R Bharadwaj
> <arun@linux.vnet.ibm.com> wrote:
>> Move paio_cancel() to new infrastructure and introduce
>> the necessary APIs for this.
>>
>> Signed-off-by: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
>> ---
>>  posix-aio-compat.c |   92 ++++++++++++++++++++++++++++++++++++++++++----------
>>  1 files changed, 74 insertions(+), 18 deletions(-)
> 
> This commit is not a safe step to make.  paio_cancel() is going to
> cause uninitialized threadlet structures to be accessed.
> 
> You split the patches up into smaller commits for easier review.
> Unfortunately this particular commit will result in a QEMU which
> builds successfully but has undefined behavior at runtime - it may
> crash or do random things.
> 
> That's a problem for git-bisect(1) and in general for anyone who
> assumes they can build QEMU at an arbitrary point in the commit
> history.  It's really important to preserve bisectability, because
> once commits get introduced that build bad QEMUs we can no longer have
> confidence in bisect!
> 
> Please split up commits so they introduce a new feature incrementally
> but work properly at each step in the series.

Arun, you may move this to later part of the series to take care of this bisect
issue.

Thanks,
JV

> 
> Stefan
> 

  reply	other threads:[~2010-12-01  3:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 18:06 [Qemu-devel] [PATCH 0/6] v12: Threadlets: A generic task offloading framework Arun R Bharadwaj
2010-11-18 18:06 ` [Qemu-devel] [PATCH 1/6] Make the necessary changes in Makefile and configure file Arun R Bharadwaj
2010-11-19  9:55   ` Stefan Hajnoczi
2010-11-18 18:06 ` [Qemu-devel] [PATCH 2/6] Move paio_cancel() to new infrastructure Arun R Bharadwaj
2010-11-19 10:07   ` Stefan Hajnoczi
2010-11-30 23:20     ` Venkateswararao Jujjuri (JV) [this message]
2010-11-18 18:07 ` [Qemu-devel] [PATCH 3/6] Move qemu_paio_submit() to the " Arun R Bharadwaj
2010-11-30 23:22   ` Venkateswararao Jujjuri (JV)
2010-11-18 18:07 ` [Qemu-devel] [PATCH 4/6] Cleanup posix-aio.compat.c off all the old code Arun R Bharadwaj
2010-11-30 23:23   ` Venkateswararao Jujjuri (JV)
2010-11-18 18:07 ` [Qemu-devel] [PATCH 5/6] Move threadlets infrastructure to qemu-threadlets.c Arun R Bharadwaj
2010-11-30 23:18   ` Venkateswararao Jujjuri (JV)
2010-11-18 18:07 ` [Qemu-devel] [PATCH 6/6] Add helper functions to enable virtio-9p make use of the threadlets Arun R Bharadwaj
2010-11-19 10:17   ` Stefan Hajnoczi
2010-11-30 23:17     ` Venkateswararao Jujjuri (JV)

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=4CF586C1.4070405@linux.vnet.ibm.com \
    --to=jvrao@linux.vnet.ibm.com \
    --cc=arun@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).