From: Vincent Lefevre <vincent@vinc17.net>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Account for grouping in printf width (bug 23432)
Date: Thu, 2 Feb 2023 14:10:21 +0100 [thread overview]
Message-ID: <20230202131021.GA3235488@cventin.lip.ens-lyon.fr> (raw)
In-Reply-To: <9531aa0c-bb05-ab2f-fd48-0751fb6f4393@redhat.com>
On 2023-01-22 18:20:52 -0500, Carlos O'Donell wrote:
> On 1/21/23 06:40, Florian Weimer wrote:
> > * Andreas Schwab via Libc-alpha:
> >
> >> diff --git a/stdio-common/Makefile b/stdio-common/Makefile
> >> index 6e9d104524..b46d932a20 100644
> >> --- a/stdio-common/Makefile
> >> +++ b/stdio-common/Makefile
> >> @@ -195,6 +195,7 @@ tests := \
> >> tst-gets \
> >> tst-grouping \
> >> tst-grouping2 \
> >> + tst-grouping3 \
> >> tst-long-dbl-fphex \
> >> tst-memstream-string \
> >> tst-obprintf \
> >
> > Missing $(gen-locales) dependency. The change itself seems okay, it
> > seems to align with POSIX. Not sure if this is still possibly to
> > apply during the freeze.
>
> I'd like to avoid a partial fix like this just before we release 2.27.
2.37
> My preference would be to review this more thoroughly, apply it when
> 2.28 opens, and then backport when we have confidence the issue is
^^^^ 2.38
> resolved.
There's actually another bug, which is a regression in glibc 2.37
and a security issue (possible buffer overflow resulting from this
new bug, as additional characters are output):
https://sourceware.org/bugzilla/show_bug.cgi?id=30068
and according to
https://sourceware.org/bugzilla/show_bug.cgi?id=30068#c5
this patch fixes this new bug.
(In bug 23432, I was considering only the precision field, while
in bug 30068, this is the width field, though these issues may be
related in the implementation.)
--
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-02-02 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 11:50 Andreas Schwab
2023-01-21 11:40 ` Florian Weimer
2023-01-22 23:20 ` Carlos O'Donell
2023-02-02 9:51 ` Andreas Schwab
2023-02-02 10:45 ` Florian Weimer
2023-02-02 10:54 ` Andreas Schwab
2023-02-02 12:00 ` Xi Ruoyao
2023-02-02 13:10 ` Vincent Lefevre [this message]
2023-02-02 13:40 ` Carlos O'Donell
2023-02-04 16:22 ` Carlos O'Donell
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=20230202131021.GA3235488@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).