From: Eric Blake <eblake@redhat.com>
To: Jack Schwartz <jack.schwartz@oracle.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, konrad.wilk@oracle.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v1 1/1] block: Add numeric errno field to BLOCK_IO_ERROR events
Date: Thu, 21 Dec 2017 19:15:24 -0600 [thread overview]
Message-ID: <ec5acd29-86ea-5972-ffa2-2d79bc377e2e@redhat.com> (raw)
In-Reply-To: <b03b4cde-5ec4-b3f0-23f6-5fc4115814d1@redhat.com>
On 12/21/2017 07:08 PM, Eric Blake wrote:
>> #
>> +# @errno: int describing the error cause, provided for applications.
>> +# (Note: while most errnos are posix compliant between OSs, it
>> +# is possible some errno values can vary among different OSs.)
>> +# (since 2.12)
>
> The proof is in the pudding - if your documentation has to give this big
> disclaimer, then what you are adding is not portable and should not be
> added in that manner.
To follow up to myself, POSIX explicitly says that errno values are
implementation dependent, and there is NO requirement that errno value 1
be EPERM, for example. And while qemu does not target GNU Hurd, that is
a classic example of a system where errno values intentionally do not
fit in 8 bits. So you can't argue that there are "POSIX-compliant errno
values", because POSIX doesn't mandate specific values.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2017-12-22 1:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 0:11 [Qemu-devel] [PATCH v1 0/1] block: Add numeric errno field to BLOCK_IO_ERROR events Jack Schwartz
2017-12-22 0:11 ` [Qemu-devel] [PATCH v1 1/1] " Jack Schwartz
2017-12-22 1:08 ` Eric Blake
2017-12-22 1:15 ` Eric Blake [this message]
2017-12-22 13:52 ` Kevin Wolf
2018-01-08 19:57 ` Jack Schwartz
2018-01-09 10:24 ` Kevin Wolf
2018-01-10 21:28 ` Jack Schwartz
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=ec5acd29-86ea-5972-ffa2-2d79bc377e2e@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jack.schwartz@oracle.com \
--cc=konrad.wilk@oracle.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).