public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/11190] regexec.c: avoid overflow in computing re_malloc buffer size (re_search_internal) Date: Fri, 22 Jan 2010 20:16:00 -0000 [thread overview] Message-ID: <20100122201620.16638.qmail@sourceware.org> (raw) In-Reply-To: <20100119155431.11190.jim@meyering.net> ------- Additional Comments From drepper at redhat dot com 2010-01-22 20:16 ------- Checked into git. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED http://sourceware.org/bugzilla/show_bug.cgi?id=11190 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
prev parent reply other threads:[~2010-01-22 20:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-19 15:54 [Bug regex/11190] New: " jim at meyering dot net 2010-01-19 15:56 ` [Bug regex/11190] " jim at meyering dot net 2010-01-19 15:58 ` jim at meyering dot net 2010-01-22 20:16 ` drepper 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=20100122201620.16638.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@sources.redhat.com \ /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).