From: Andreas Schwab <schwab@suse.de>
To: Jonny Grant <jg@jguk.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>,
Xi Ruoyao <xry111@xry111.site>
Subject: Re: glibc misc/sys/cdefs.h nonull - typo in comment
Date: Mon, 30 Oct 2023 10:04:51 +0100 [thread overview]
Message-ID: <mvmo7gg7a6k.fsf@suse.de> (raw)
In-Reply-To: <984eaee1-251f-4917-91f3-d19b5f8a95bc@jguk.org> (Jonny Grant's message of "Sun, 29 Oct 2023 22:43:48 +0000")
On Okt 29 2023, Jonny Grant wrote:
> glibc does go beyond POSIX and set errno to EFAULT if a null pointer constant is passed.
> https://man7.org/linux/man-pages/man2/olduname.2.html
>
> Although I looked at glibc/posix/uname.c and it has EINVAL there, couldn't spot where the EFAULT comes from, probably there is another file.
glibc never generates EFAULT on its own, it always comes from the
kernel.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-10-30 9:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 9:09 Jonny Grant
2023-04-11 13:39 ` Adhemerval Zanella Netto
2023-04-12 15:56 ` Jonny Grant
2023-04-12 16:26 ` Xi Ruoyao
2023-04-12 16:31 ` Xi Ruoyao
2023-10-28 23:50 ` Jonny Grant
2023-10-29 5:24 ` Paul Eggert
2023-10-29 22:43 ` Jonny Grant
2023-10-30 9:04 ` Andreas Schwab [this message]
2023-10-30 10:10 ` Xi Ruoyao
2023-12-03 22:09 ` Jonny Grant
2023-11-01 7:38 ` Florian Weimer
2023-11-01 19:30 ` Paul Eggert
2023-11-01 19:52 ` Jonny Grant
2023-11-01 20:05 ` Florian Weimer
2023-11-01 20:16 ` Jonny Grant
2023-11-01 20:06 ` Florian Weimer
2023-04-12 17:28 ` Adhemerval Zanella Netto
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=mvmo7gg7a6k.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=eggert@cs.ucla.edu \
--cc=jg@jguk.org \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).