unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao via Libc-alpha <libc-alpha@sourceware.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Xi Ruoyao via Libc-alpha <libc-alpha@sourceware.org>
Cc: Alejandro Colomar <alx.manpages@gmail.com>
Subject: Re: bind(2): Missing [[gnu::nonnull]]
Date: Sun, 04 Dec 2022 13:59:48 +0800	[thread overview]
Message-ID: <ddbccfdcccaedafc6101e2aa283492f19823a947.camel@xry111.site> (raw)
In-Reply-To: <87wn78cnpe.fsf@igel.home>

On Sat, 2022-12-03 at 20:05 +0100, Andreas Schwab wrote:
> > Currently the man page says:
> > 
> > EFAULT: addr points outside the user's accessible address space.
> > 
> > And bind(2) indeed sets errno to EFAULT and return -1 when NULL is
> > passed as addr.
> 
> You can never depend on EFAULT for invalid addresses.

Hmm, is this documented somewhere?

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  parent reply	other threads:[~2022-12-04  6:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03 15:33 bind(2): Missing [[gnu::nonnull]] Alejandro Colomar via Libc-alpha
2022-12-03 15:55 ` Xi Ruoyao via Libc-alpha
2022-12-03 16:41   ` Alejandro Colomar via Libc-alpha
2022-12-03 19:05   ` Andreas Schwab
2022-12-03 19:12     ` Alejandro Colomar via Libc-alpha
2022-12-04  5:59     ` Xi Ruoyao via Libc-alpha [this message]
2022-12-04 11:14       ` Alejandro Colomar via Libc-alpha
2022-12-04 18:46         ` Florian Weimer via Libc-alpha
2022-12-05 18:53           ` Zack Weinberg via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ddbccfdcccaedafc6101e2aa283492f19823a947.camel@xry111.site \
    --to=libc-alpha@sourceware.org \
    --cc=alx.manpages@gmail.com \
    --cc=schwab@linux-m68k.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).