public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/27857] swprintf does not output a null character when output would be too long
Date: Mon, 19 Dec 2022 18:56:51 +0000	[thread overview]
Message-ID: <bug-27857-131-Kj4di4OSKX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27857-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=118816de3383ff12769349784689141355cc787c

commit 118816de3383ff12769349784689141355cc787c
Author: Florian Weimer <fweimer@redhat.com>
Date:   Mon Dec 19 18:56:55 2022 +0100

    libio: Convert __vswprintf_internal to buffers (bug 27857)

    Always null-terminate the buffer and set E2BIG if the buffer is too
    small.  This fixes bug 27857.

    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

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

  parent reply	other threads:[~2022-12-19 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:16 [Bug stdio/27857] New: " warp at iki dot fi
2022-03-17 18:33 ` [Bug stdio/27857] " fweimer at redhat dot com
2022-12-19 18:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-15 10:35 ` fweimer 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-27857-131-Kj4di4OSKX@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).