From: Kevin Wolf <kwolf@redhat.com>
To: Pino Toscano <ptoscano@redhat.com>
Cc: libguestfs@redhat.com, "Richard W.M. Jones" <rjones@redhat.com>,
qemu block <qemu-block@nongnu.org>,
mreitz@redhat.com,
"Qemu-devel@nongnu.org" <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] [Libguestfs] [PATCH] tests: regressions: make test-big-heap use a temporary empty file
Date: Wed, 21 Mar 2018 21:44:20 +0100 [thread overview]
Message-ID: <20180321204420.GL3898@localhost.localdomain> (raw)
In-Reply-To: <2075074.dXtERdIzXi@thyrus.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]
Am 21.03.2018 um 14:48 hat Pino Toscano geschrieben:
> On Wednesday, 21 March 2018 14:45:38 CET Eric Blake wrote:
> > [adding qemu lists]
> >
> > On 03/21/2018 07:51 AM, Richard W.M. Jones wrote:
> > > On Wed, Mar 21, 2018 at 01:44:17PM +0100, Pino Toscano wrote:
> > >> Newer versions of qemu use file locking for the images by default, and
> > >> apparently that does not work with /dev/null. Since this test just
> > >> calls qemu-img to get the format of an empty image, create a temporary
> > >> one instead.
> > >
> > > ACK, but feels like this is a bug in qemu-img to me.
> >
> > You're right that file locking on a character device like /dev/null is
> > not going to work as expected, but is it a case where fcntl() actually
> > fails, or is it worse where the fcntl() claiming the locks "succeeds"
> > but doesn't do what we want? That is, what were the actual error
> > messages you ran into?
>
> $ qemu-img --version
> qemu-img version 2.10.1(qemu-2.10.1-2.fc27)
> Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
> $ qemu-img info /dev/null
> qemu-img: Could not open '/dev/null': Failed to get "consistent read" lock
> Is another process using the image?
Not sure where the difference is, but I can't reproduce this on
upstream, neither git master nor the v2.10.1 tag:
$ ./qemu-img --version
qemu-img version 2.10.1 (v2.10.1-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
$ ./qemu-img info /dev/null
image: /dev/null
file format: raw
virtual size: 0 (0 bytes)
disk size: 0
Also with strace:
open("/dev/null", O_RDONLY|O_CLOEXEC) = 10
fcntl(10, F_OFD_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=100, l_len=1}) = 0
...
So my kernel (4.15.9-200.fc26.x86_64) seems to have no problems with
locking /dev/null.
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-03-21 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180321124417.29242-1-ptoscano@redhat.com>
[not found] ` <20180321125105.GJ19514@redhat.com>
2018-03-21 13:45 ` [Qemu-devel] [Libguestfs] [PATCH] tests: regressions: make test-big-heap use a temporary empty file Eric Blake
2018-03-21 13:48 ` Pino Toscano
2018-03-21 20:44 ` Kevin Wolf [this message]
2018-03-21 20:58 ` [Qemu-devel] [Qemu-block] " Eric Blake
2018-03-21 22:15 ` Richard W.M. Jones
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=20180321204420.GL3898@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=libguestfs@redhat.com \
--cc=mreitz@redhat.com \
--cc=ptoscano@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=rjones@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).