From: Rich Felker <dalias@libc.org>
To: Matthew Fernandez <matthew.fernandez@nicta.com.au>
Cc: musl@lists.openwall.com
Subject: Re: Undetected failures in getdomainname
Date: Wed, 22 Jun 2016 12:31:51 -0400 [thread overview]
Message-ID: <20160622163151.GP10893@brightrain.aerifal.cx> (raw)
In-Reply-To: <576A491D.7030509@nicta.com.au>
On Wed, Jun 22, 2016 at 06:15:25PM +1000, Matthew Fernandez wrote:
> Hi all,
>
> In the tip at time of writing
> (6cec7bc57f599f43f4041cec2093e3c9231dbaab) there are a couple of
> syscalls that are implemented by calling uname, notably gethostname
> and getdomainname. In gethostname, the return value of uname is
> checked and the code returns early if uname fails. However, in
> getdomainname the return value of uname is ignored. I think it
> should be following the same pattern as gethostname. Is this
> correct?
In practice I don't think the difference matters unless someone has
hooked uname to fail (e.g. seccomp or perhaps LSMs), since the syscall
itself can't fail. It wouldn't hurt to make them consistent though.
> Also, gethostname rolls its own strcpy, while getdomainname just
> calls strcpy. However, maybe there is a good reason for this.
As written the behaviors are different. gethostname truncates while
getdomainname returns an error on excessive length. The former is
mandated by POSIX; the latter is documented (but not clearly specified
as a requirement vs just being an optional failure) in the Linux man
page, since getdomainname is not a standard function.
Rich
next prev parent reply other threads:[~2016-06-22 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 8:15 Matthew Fernandez
2016-06-22 16:31 ` Rich Felker [this message]
2016-06-23 0:17 ` Matthew Fernandez
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=20160622163151.GP10893@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=matthew.fernandez@nicta.com.au \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).