From: Rich Felker <dalias@libc.org>
To: Ismael Luceno <ismael@iodev.co.uk>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] fix avoidable segfault in catclose
Date: Thu, 25 Jan 2024 10:56:54 -0500 [thread overview]
Message-ID: <20240125155653.GI4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <ZbJ-LzMkjtb5lMwc@pirotess>
On Thu, Jan 25, 2024 at 04:28:47PM +0100, Ismael Luceno wrote:
> <...>
> > Generally in musl, we prefer to trap on UB rather than allowing
> > forward progress, especially when the natural default action without
> > special casing it is to trap.
>
> POSIX says: "The catclose() function may fail if: [EBADF] The catalog
> descriptor is not valid. ..."
>
> Implying a known invalid descriptor like -1, or an invalidated
> descriptor should be handled.
>
> Glibc manual says:
> "... Errors can occur if the catalog descriptor catalog_desc is not
> valid in which case errno is set to EBADF."
>
> The linux manpage also says that once closed, the descriptor gets
> invalidated, which isn't what we're doing here.
This is not a "should be handled". "May fail" is always optional and
is a redundant allowance we explicitly do not use when the behavior is
UB. (It's redundant because anything can happen in the event of UB;
you don't need an allowance for that.)
Here, the API is designed around the possibility that cat_t may be
implemented as some sort of descriptor where it's possible/tractable
to identify valid vs invalid values, and presumably that's where the
idea of EBADF came from. But even EBADF in general is a bad idea, and
not something we'd want to implement except where required. EBADF
basically always indicates a dangerous UAF or DF type bug, where
trapping is the preferred behavior.
The philosophy behind this is explained in the *glibc* wiki, where the
relevant text (10.4.1 NULL pointers) was copied from an answer of mine
on Stack Overflow long ago:
https://sourceware.org/glibc/wiki/Style_and_Conventions#Bugs_in_the_user_program
Rich
next prev parent reply other threads:[~2024-01-25 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 7:09 Ismael Luceno
2024-01-25 14:05 ` Rich Felker
2024-01-25 15:28 ` Ismael Luceno
2024-01-25 15:56 ` Rich Felker [this message]
2024-01-25 14:11 ` Markus Wichmann
2024-01-25 15:30 ` Ismael Luceno
2024-01-25 20:10 ` [musl] RE: [EXTERNAL] " Andy Caldwell
2024-01-25 21:25 ` Rich Felker
2024-01-26 17:13 ` Andy Caldwell
2024-01-26 17:27 ` Rich Felker
2024-01-26 19:12 ` Andy Caldwell
2024-01-26 19:57 ` Rich Felker
2024-01-26 20:16 ` Andy Caldwell
2024-01-27 11:04 ` Szabolcs Nagy
2024-01-27 12:58 ` Alexander Monakov
2024-01-27 14:56 ` Rich Felker
2024-01-27 19:20 ` Szabolcs Nagy
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=20240125155653.GI4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=ismael@iodev.co.uk \
--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).