From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, mreitz@redhat.com,
"Richard W.M. Jones" <rjones@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu-nbd: only send a limited number of errno codes on the wire
Date: Fri, 08 May 2015 06:35:28 -0600 [thread overview]
Message-ID: <554CAD90.3060300@redhat.com> (raw)
In-Reply-To: <554C8FAF.1080207@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
On 05/08/2015 04:27 AM, Paolo Bonzini wrote:
>
>
> On 08/05/2015 12:12, Markus Armbruster wrote:
>>> The corresponding patch to the NBD protocol description can be found at
>>> http://article.gmane.org/gmane.linux.drivers.nbd.general/3154.
>
> [...]
>
>>> - EFBIG is part of the universal set of errors, but it is also changed
>>> to ENOSPC because it is pretty similar to ENOSPC or EDQUOT.
>>
>> Perhaps debatable, but I defer to your judgement.
>
> EFBIG is weird anyway, and requires you (or your parents) to ignore
> SIGXFSZ. A simpler protocol puts fewer requirements on the client.
Not only that, but if I understand correctly, the only way to trigger
SIGXFSZ or EFBIG is to compile your application to use a smaller off_t
than the maximum the system supports. That is, it is impossible on
64-bit Linux, and on 32-bit Linux is it possible only when you use
32-bit off_t instead of 64-bit off_t. But we are dealing with guest
disk images, and practically require 64-bit off_t to make it useful for
all but the oldest of guests.
>
> (In fact, we probably should ignore SIGXFSZ in QEMU and treat EFBIG like
> ENOSPC everywhere. Should doesn't mean that it will get on anyone's
> todo list or priority list...).
and if I'm right above, it wouldn't make a difference anyway.
--
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: 604 bytes --]
next prev parent reply other threads:[~2015-05-08 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 9:50 [Qemu-devel] [PATCH v2] qemu-nbd: only send a limited number of errno codes on the wire Paolo Bonzini
2015-05-08 10:12 ` Markus Armbruster
2015-05-08 10:27 ` Paolo Bonzini
2015-05-08 10:40 ` Richard W.M. Jones
2015-05-08 12:35 ` Eric Blake [this message]
2015-05-08 12:40 ` Eric Blake
2015-05-08 12:41 ` Paolo Bonzini
2015-05-08 13:02 ` Eric Blake
2015-05-08 13:04 ` Paolo Bonzini
2015-05-09 14:29 ` Thomas Schwinge
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=554CAD90.3060300@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).