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 libc/17062] fnmatch: buffer overflow read from pattern "[[:alpha:]'[:alpha:]" Date: Wed, 18 Jun 2014 12:21:00 -0000 [thread overview] Message-ID: <bug-17062-131-yeG4ttYarK@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17062-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17062 --- Comment #1 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, master has been updated via b3a9f56ba59c3d8eadd3135a1c25c37a63151450 (commit) from 85d89278568b4191da3b2fee589553e90b54ffa5 (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=b3a9f56ba59c3d8eadd3135a1c25c37a63151450 commit b3a9f56ba59c3d8eadd3135a1c25c37a63151450 Author: Andreas Schwab <schwab@suse.de> Date: Wed Jun 18 11:58:45 2014 +0200 Don't read past end of pattern in fnmatch (BZ #17062) ----------------------------------------------------------------------- Summary of changes: ChangeLog | 8 ++++++++ NEWS | 2 +- posix/Makefile | 3 ++- posix/fnmatch_loop.c | 13 +++---------- stdlib/tst-system.c => posix/tst-fnmatch3.c | 14 +++++++------- 5 files changed, 21 insertions(+), 19 deletions(-) copy stdlib/tst-system.c => posix/tst-fnmatch3.c (77%) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-18 12:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-17 15:22 [Bug regex/17062] New: " konstantin.s.serebryany at gmail dot com 2014-06-17 17:37 ` [Bug libc/17062] " jsm28 at gcc dot gnu.org 2014-06-18 12:21 ` cvs-commit at gcc dot gnu.org [this message] 2014-06-18 12:25 ` schwab@linux-m68k.org 2014-06-19 15:06 ` bugdal at aerifal dot cx 2015-02-18 14:32 ` 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-17062-131-yeG4ttYarK@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).