public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/29090] strfmon does not set E2BIG when buffer is too small
Date: Tue, 26 Apr 2022 09:18:28 +0000	[thread overview]
Message-ID: <bug-29090-131-O46MtGJKM9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29090-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29090

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
I believe my vfprintf series fixes this:

[PATCH 20/26] stdio-common: Convert vfprintf and related functions to buffers
https://sourceware.org/pipermail/libc-alpha/2022-March/137154.html

Specifically, the new implementation does not use a temporary string buffer.
Instead, __printf_fp_l_buffer writes directly to the strfmon buffer that sets
E2BIG on overflow. We should add a test case for this, though.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2022-04-26  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  8:30 [Bug locale/29090] New: " kamilcukrowski at gmail dot com
2022-04-26  9:18 ` fweimer at redhat dot com [this message]
2023-04-13 14:21 ` [Bug locale/29090] " schwab@linux-m68k.org

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=bug-29090-131-O46MtGJKM9@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).