From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 214171] New: I am not sure why the definition of EAI_SYSTEM, from getaddrinfo, was changed from POSIX
Date: Wed, 25 Aug 2021 14:49:59 +0000 [thread overview]
Message-ID: <bug-214171-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214171
Bug ID: 214171
Summary: I am not sure why the definition of EAI_SYSTEM, from
getaddrinfo, was changed from POSIX
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: christian.morales.vega@gmail.com
Regression: No
https://man7.org/linux/man-pages/man3/freeaddrinfo.3p.html says:
"[EAI_SYSTEM] A system error occurred; the error code can be found in errno."
Which makes a lot of sense. The function can fall because of name-resolution
specific problem (EAI_NODATA). But otherwise it must be a plain old generic
error that can be expressed with errno, so you should look in errno.
It's not explicitly said. But IMHO it's clear that it would be a bug to return
EAI_SYSTEM without setting errno/setting errno to zero.
But then https://man7.org/linux/man-pages/man3/getaddrinfo.3.html replaces it
with:
"EAI_SYSTEM Other system error, check errno for details."
Which, I'm not a native speaker, but it seems to me to leave returning
EAI_SYSTEM and setting errno to 0 more open to interpretation. You can argue
that in such a case errno == 0 simply means "no details".
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-08-25 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 14:49 bugzilla-daemon [this message]
2021-08-25 15:41 ` [Bug 214171] I am not sure why the definition of EAI_SYSTEM, from getaddrinfo, was changed from POSIX bugzilla-daemon
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=bug-214171-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 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.