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/17269] _IO_wstr_overflow integer overflow Date: Tue, 21 Jul 2015 02:38:00 -0000 [thread overview] Message-ID: <bug-17269-131-tn8p9z8aQM@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17269-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17269 --- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The branch, release/2.21/master has been updated via 8a4e5cc6574a419d5724bef6be98d705d58db48d (commit) from fe7b1136e5753c85b3ccc8395dfc66b82052d73c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8a4e5cc6574a419d5724bef6be98d705d58db48d commit 8a4e5cc6574a419d5724bef6be98d705d58db48d Author: Paul Pluzhnikov <ppluzhnikov@google.com> Date: Sun Feb 22 12:01:47 2015 -0800 Fix BZ #17269 -- _IO_wstr_overflow integer overflow (cherry picked from commit bdf1ff052a8e23d637f2c838fa5642d78fcedc33) ----------------------------------------------------------------------- Summary of changes: ChangeLog | 6 ++++++ NEWS | 2 +- libio/wstrops.c | 8 +++++++- 3 files changed, 14 insertions(+), 2 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-21 2:38 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-14 16:45 [Bug stdio/17269] New: " jsm28 at gcc dot gnu.org 2015-02-18 13:25 ` [Bug stdio/17269] " fweimer at redhat dot com 2015-02-18 14:20 ` fweimer at redhat dot com 2015-02-22 5:23 ` ppluzhnikov at google dot com 2015-02-22 20:03 ` cvs-commit at gcc dot gnu.org 2015-02-22 20:05 ` ppluzhnikov at google dot com 2015-07-21 2:34 ` vapier at gentoo dot org 2015-07-21 2:36 ` vapier at gentoo dot org 2015-07-21 2:38 ` cvs-commit at gcc dot gnu.org [this message] 2015-07-21 3:52 ` cvs-commit at gcc dot gnu.org 2015-10-19 9:51 ` cvs-commit at gcc dot gnu.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-17269-131-tn8p9z8aQM@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).