From: Aleksa Sarai <cyphar@cyphar.com>
To: Eric Rannaud <eric.rannaud@gmail.com>
Cc: linux-api@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: clock_settime(2) error for non-settable clocks
Date: Sat, 21 Mar 2020 14:56:57 +1100 [thread overview]
Message-ID: <20200321035657.6baexoov65dkpmsb@yavin.dot.cyphar.com> (raw)
In-Reply-To: <CA+zRj8U5_NaY4ZQXj9r=f58KcO3pq5k9HZt9KxRYHnOOk=e1WQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
On 2020-03-20, Eric Rannaud <eric.rannaud@gmail.com> wrote:
> Should we update the manpage to more fully explain the range of
> possible errors or instead try to have more consistent errors? For
> syscalls, what's the backward-compatibility contract for errno values?
It's the same as everything else -- "if it breaks an existing
application, it's a regression". There was an infamous case of this
exact scenario happening (changing the errno returned from an ioctl
broke pulseaudio) in 2012[1].
[1]: https://lore.kernel.org/lkml/CA+55aFzX56kPPwSO97X=UyPaMzV5QRNG9ScN=nxnHFjmz=_8yA@mail.gmail.com/
--
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
<https://www.cyphar.com/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-03-21 3:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 18:02 clock_settime(2) error for non-settable clocks Eric Rannaud
2020-03-21 3:56 ` Aleksa Sarai [this message]
2020-03-26 8:37 ` Michael Kerrisk (man-pages)
2020-03-29 20:49 ` Michael Kerrisk (man-pages)
2020-04-02 11:48 ` Michael Kerrisk (man-pages)
2020-04-02 14:23 ` [PATCH 1/1] clock_getres.2: dynamic POSIX clock devices can return other errors Eric Rannaud
2020-04-02 19:55 ` Michael Kerrisk (man-pages)
2020-04-02 20:06 ` Eric Rannaud
2020-04-02 20:19 ` Michael Kerrisk (man-pages)
2020-04-02 20:49 ` Eric Rannaud
2020-04-02 20:50 ` Eric Rannaud
2020-04-03 7:02 ` Michael Kerrisk (man-pages)
2020-04-03 16:42 ` Eric Rannaud
2020-04-20 11:13 ` Michael Kerrisk (man-pages)
2020-04-02 14:29 ` clock_settime(2) error for non-settable clocks Eric Rannaud
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=20200321035657.6baexoov65dkpmsb@yavin.dot.cyphar.com \
--to=cyphar@cyphar.com \
--cc=eric.rannaud@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.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).