From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: famz@redhat.com, tony@bakeyournoodle.com, qemu-devel@nongnu.org,
stefanha@redhat.com, pbonzini@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 3/4] raw-posix: Fix try_seek_hole()'s handling of SEEK_DATA failure
Date: Thu, 13 Nov 2014 07:52:10 -0700 [thread overview]
Message-ID: <5464C59A.4000602@redhat.com> (raw)
In-Reply-To: <20141113130327.GD3933@noname.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
On 11/13/2014 06:03 AM, Kevin Wolf wrote:
> Am 13.11.2014 um 11:17 hat Markus Armbruster geschrieben:
>> When SEEK_HOLE tells us we're in a hole, we try SEEK_DATA to find its
>> end. When that fails, we pretend the hole extends to the end of file.
>> Wrong.
>
> Wrong only in some cases, see below.
>
>> Except when SEEK_END fails, we screw up and claim it extends
>> to offset -1. More wrong.
>> +++ b/block/raw-posix.c
>> @@ -1494,8 +1494,9 @@ static int try_seek_hole(BlockDriverState *bs, off_t start, off_t *data,
>> } else {
>> /* On a hole. We need another syscall to find its end. */
>> *data = lseek(s->fd, start, SEEK_DATA);
>> - if (*data == -1) {
>> - *data = lseek(s->fd, 0, SEEK_END);
>> + if (*data < 0) {
>> + /* no idea where the hole ends, give up (unlikely to happen) */
>
> Not quite unlikely. If the file ends with a sparse area, we'll get
> -1/ENXIO here.
>
> lseek() with SEEK_DATA starting in a hole when there is no data until
> EOF is actually the part that isn't documented in the man page, but
> ENXIO is what I'm seeing here on RHEL 7.
Here's the (proposed) POSIX wording:
http://austingroupbugs.net/view.php?id=415
And ENXIO is indeed the expected error for SEEK_DATA on a trailing hole,
so maybe we should special case it.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-11-13 14:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 10:16 [Qemu-devel] [PATCH v2 0/4] raw-posix: Get rid of FIEMAP, and more Markus Armbruster
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 1/4] raw-posix: Fix comment for raw_co_get_block_status() Markus Armbruster
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 2/4] raw-posix: SEEK_HOLE suffices, get rid of FIEMAP Markus Armbruster
2014-11-13 10:19 ` Max Reitz
2014-11-13 14:09 ` Eric Blake
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 3/4] raw-posix: Fix try_seek_hole()'s handling of SEEK_DATA failure Markus Armbruster
2014-11-13 10:22 ` Max Reitz
2014-11-13 13:03 ` Kevin Wolf
2014-11-13 14:52 ` Eric Blake [this message]
2014-11-13 15:29 ` Eric Blake
2014-11-13 15:44 ` Max Reitz
2014-11-13 15:49 ` Eric Blake
2014-11-13 15:52 ` Eric Blake
2014-11-13 15:47 ` Eric Blake
2014-11-13 16:01 ` Eric Blake
2014-11-14 13:12 ` Markus Armbruster
2014-11-15 0:47 ` Eric Blake
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 4/4] raw-posix: Clean up around raw_co_get_block_status() Markus Armbruster
2014-11-13 10:27 ` Max Reitz
2014-11-13 12:48 ` Markus Armbruster
2014-11-13 13:30 ` [Qemu-devel] [PATCH v2 0/4] raw-posix: Get rid of FIEMAP, and more Eric Blake
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=5464C59A.4000602@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tony@bakeyournoodle.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 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.