From: Vincent Lefevre <vincent@vinc17.net>
To: libc-alpha@sourceware.org
Subject: Re: UB status of snprintf on invalid ptr+size combination?
Date: Mon, 20 Mar 2023 18:45:46 +0100 [thread overview]
Message-ID: <20230320174546.GI203866@cventin.lip.ens-lyon.fr> (raw)
In-Reply-To: <e675a1ae-a19f-4ab2-84f5-f8b9fcd08697@gotplt.org>
On 2023-03-20 13:31:33 -0400, Siddhesh Poyarekar wrote:
> In glibc we tend to skip a test as UNSUPPORTED when resources to run a test
> are considered uncommon (from the perspective of a test system) and cannot
> be expected to be met in all environments.
In MPFR, we have some tests that need much memory, which are enabled
only if the MPFR_CHECK_LARGEMEM environment variable is set. But this
means that some issues would not be detected on particular platforms
by end users (MPFR_CHECK_LARGEMEM is mainly for developers).
> It looks like mpfr_snprintf and glibc snprintf are incompatible in this
> context and the latter should not be used to implement the former if the n >
> __bos(dest) use case is important to it.
>
> Then again, I wish mpfr_snprintf also similarly tightened its requirements,
> but that's a discussion for another day.
Well, if the C standard is changed, I suppose that we will align to
it. We can still recommend not to use n > buffer size if this is not
supported by snprintf (even though the MPFR code is currently
guaranteed to work in this case).
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2023-03-20 17:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 19:47 Simon Chopin
2023-03-14 21:39 ` Paul Eggert
2023-03-15 9:22 ` Andreas Schwab
2023-03-15 15:54 ` Siddhesh Poyarekar
2023-03-15 18:34 ` Michael Hudson-Doyle
2023-03-19 14:45 ` manfred
2023-03-19 23:07 ` Vincent Lefevre
2023-03-20 12:05 ` Siddhesh Poyarekar
2023-03-20 12:17 ` Alejandro Colomar
2023-03-20 12:29 ` Siddhesh Poyarekar
2023-03-20 13:36 ` Vincent Lefevre
2023-03-20 13:50 ` Vincent Lefevre
2023-03-20 16:56 ` Siddhesh Poyarekar
2023-03-20 17:36 ` Vincent Lefevre
2023-03-20 15:09 ` Vincent Lefevre
2023-03-20 16:15 ` Alejandro Colomar
2023-03-20 16:33 ` Vincent Lefevre
2023-03-20 17:00 ` Vincent Lefevre
2023-03-20 17:31 ` Siddhesh Poyarekar
2023-03-20 17:45 ` Vincent Lefevre [this message]
2023-03-15 12:39 ` Vincent Lefevre
2023-03-16 10:29 ` Stephan Bergmann
2023-03-18 2:07 ` Vincent Lefevre
2023-03-18 2:30 ` Alejandro Colomar
2023-03-18 10:58 ` Vincent Lefevre
2023-03-18 15:01 ` Andreas Schwab
2023-03-19 22:48 ` Vincent Lefevre
2023-03-19 23:24 ` Andreas Schwab
2023-03-20 4:10 ` Vincent Lefevre
2023-03-20 9:19 ` Andreas Schwab
2023-03-20 10:42 ` Vincent Lefevre
2023-03-20 10:44 ` Andreas Schwab
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=20230320174546.GI203866@cventin.lip.ens-lyon.fr \
--to=vincent@vinc17.net \
--cc=libc-alpha@sourceware.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 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).