Re: [Qemu-devel] [PATCH v5 5/5] iotests: chown LUKS device before qemu-io launches

2017-06-07 Thread Max Reitz
On 2017-06-01 10:40, Daniel P. Berrange wrote: > 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

Re: [Qemu-devel] [PATCH v5 5/5] iotests: chown LUKS device before qemu-io launches

2017-06-01 Thread Daniel P. Berrange
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

Re: [Qemu-devel] [PATCH v5 5/5] iotests: chown LUKS device before qemu-io launches

2017-05-31 Thread Max Reitz
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

[Qemu-devel] [PATCH v5 5/5] iotests: chown LUKS device before qemu-io launches

2017-05-09 Thread Daniel P. Berrange
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