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 stdio/31137] Regression vfprintf + setbuf (no buffering) Date: Mon, 11 Dec 2023 17:37:17 +0000 [thread overview] Message-ID: <bug-31137-131-Oi3AWOAYp6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31137-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31137 --- Comment #4 from Florian Weimer <fweimer at redhat dot com> --- I'm pretty sure the actual application has a more elaborate format string here. If we don't have a large enough buffer, that will still result in multiple writes even if we can handle arbitrarily large %s strings directly (because we need to flush the previous buffer contents due to lack of vectored writes, and write the subsequent format bits from the buffer). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-11 17:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-11 12:58 [Bug stdio/31137] New: " david.marchand at redhat dot com 2023-12-11 13:00 ` [Bug stdio/31137] " fweimer at redhat dot com 2023-12-11 13:32 ` schwab@linux-m68k.org 2023-12-11 13:48 ` fweimer at redhat dot com 2023-12-11 15:04 ` schwab@linux-m68k.org 2023-12-11 17:37 ` fweimer at redhat dot com [this message] 2024-04-16 17:21 ` carlos at redhat dot com
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-31137-131-Oi3AWOAYp6@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: linkBe 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).