All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Two small fixes to the streaming test case.
Date: Wed, 06 Jun 2012 14:41:19 +0200	[thread overview]
Message-ID: <4FCF4FEF.3090005@redhat.com> (raw)
In-Reply-To: <4FCF49D5.6060409@redhat.com>

Am 06.06.2012 14:15, schrieb Paolo Bonzini:
> 
>> A real patch series is preferable, having the patches as part of your
>> signature makes quoting them a bit harder with Thunderbird...
> 
> Oops.  Unintended, sorry.
> 
>>> From 644fda4d6da1a5babfc8884f255d87ebaf847616 Mon Sep 17 00:00:00 2001
>>> From: Paolo Bonzini <pbonzini@redhat.com>
>>> Date: Wed, 23 May 2012 13:07:56 +0200
>>> Subject: [PATCH 1/2] qemu-iotests: fill streaming test image with data
>>>
>>> This avoids that the job completes too fast when the file system
>>> reports the hole to QEMU (via FIEMAP or SEEK_HOLE).
>>>
>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>
>> Does this really fix the cause or just a symptom? The commit message
>> sounds like a race and now we happen to win it again. But maybe it's
>> just a bad wording that gives the impression.
> 
> No, unfortunately that's exactly the case.  The whole TestStreamStop
> test case is racy.
> 
> If the job completes before we can cancel it, it fails.  If we remove
> the sleep the job will be canceled before it has even started, and the
> test succeeds but I'm not sure it is testing anything worthwhile.
> 
> But if the image is left sparse, then the job has really nothing to do
> except reading one L2-table.  You're pretty much guaranteed to complete
> the job too soon, and the test fails.

Ah, you're talking about the cases where we cancel, this wasn't quite
clear and so I looked at the wrong tests. Thanks for the explanations,
the patches make sense to me now.

Can you resend a v2 as an actual patch series and use that opportunity
to make the commit messages a bit more detailed?

Kevin

      reply	other threads:[~2012-06-06 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 23:10 [Qemu-devel] [PATCH 0/2] Two small fixes to the streaming test case Paolo Bonzini
2012-06-06  8:02 ` Kevin Wolf
2012-06-06 12:15   ` Paolo Bonzini
2012-06-06 12:41     ` 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=4FCF4FEF.3090005@redhat.com \
    --to=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.