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/31183] Wide stream buffer size reduced MB_LEN_MAX bytes after bug 17522 fix Date: Tue, 02 Jan 2024 13:43:45 +0000 [thread overview] Message-ID: <bug-31183-131-V9qvnOyQui@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31183-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31183 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED Target Milestone|--- |2.39 --- Comment #2 from Florian Weimer <fweimer at redhat dot com> --- Fixed for 2.39 via: commit ecc7c3deb9f347649c2078fcc0f94d4cedf92d60 Author: Florian Weimer <fweimer@redhat.com> Date: Tue Jan 2 14:36:17 2024 +0100 libio: Check remaining buffer size in _IO_wdo_write (bug 31183) The multibyte character needs to fit into the remaining buffer space, not the already-written buffer space. Without the fix, we were never moving the write pointer from the start of the buffer, always using the single-character fallback buffer. Fixes commit 04b76b5aa8b2d1d19066e42dd1 ("Don't error out writing a multibyte character to an unbuffered stream (bug 17522)"). -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-02 13:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-20 15:43 [Bug stdio/31183] New: " fweimer at redhat dot com 2023-12-20 15:43 ` [Bug stdio/31183] " fweimer at redhat dot com 2023-12-20 16:17 ` fweimer at redhat dot com 2024-01-02 13:43 ` fweimer at redhat dot com [this message]
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-31183-131-V9qvnOyQui@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).