qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>,
	qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 5/5] iotests: chown LUKS device before qemu-io launches
Date: Thu, 1 Jun 2017 09:40:57 +0100	[thread overview]
Message-ID: <20170601084057.GD1490@redhat.com> (raw)
In-Reply-To: <1762f0c5-9881-99bb-6134-2877257d2895@redhat.com>

On Wed, May 31, 2017 at 06:15:27PM +0200, Max Reitz wrote:
> On 2017-05-09 19:33, Daniel P. Berrange wrote:
> > On some distros, whenever you close a block device file
> > descriptor there is a udev rule that resets the file
> > permissions. This can race with the test script when
> > we run qemu-io multiple times against the same block
> > device. Occasionally the second qemu-io invocation
> > will find udev has reset the permissions causing failure.
> > 
> > Reviewed-by: Eric Blake <eblake@redhat.com>
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> >  tests/qemu-iotests/149     |  13 +-
> >  tests/qemu-iotests/149.out | 344 ++++++++++++++++++++++-----------------------
> >  2 files changed, 178 insertions(+), 179 deletions(-)
> > 
> > diff --git a/tests/qemu-iotests/149 b/tests/qemu-iotests/149
> > index 5faf585..bc628ce 100755
> > --- a/tests/qemu-iotests/149
> > +++ b/tests/qemu-iotests/149
> > @@ -23,6 +23,7 @@
> >  import subprocess
> >  import os
> >  import os.path
> > +import time
> 
> Why?

That's left over cruft from debugging this test. I'll kill it.

> Rest looks good.

Does that count for "reviewed-by" if i kill the import ?

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-06-01  8:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 17:33 [Qemu-devel] [PATCH v5 0/5] Improve I/O tests coverage of LUKS Daniel P. Berrange
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 1/5] iotests: skip 159 & 170 with luks format Daniel P. Berrange
2017-05-31 15:12   ` Max Reitz
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 2/5] iotests: fix remainining tests to work with LUKS Daniel P. Berrange
2017-05-09 17:49   ` Eric Blake
2017-05-31 15:33   ` Max Reitz
2017-05-31 15:59     ` Eric Blake
2017-05-31 16:08       ` Max Reitz
2017-06-01  8:36     ` Daniel P. Berrange
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 3/5] iotests: reduce PBKDF iterations when testing LUKS Daniel P. Berrange
2017-05-31 15:41   ` Max Reitz
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 4/5] iotests: add more LUKS hash combination tests Daniel P. Berrange
2017-05-31 16:09   ` Max Reitz
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 5/5] iotests: chown LUKS device before qemu-io launches Daniel P. Berrange
2017-05-31 16:15   ` Max Reitz
2017-06-01  8:40     ` Daniel P. Berrange [this message]
2017-06-07 12:33       ` Max Reitz

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=20170601084057.GD1490@redhat.com \
    --to=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).