public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "jim at meyering dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/17150] New: regex: don't deref NULL upon heap allocation failure
Date: Sun, 13 Jul 2014 00:06:00 -0000	[thread overview]
Message-ID: <bug-17150-132@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17150
           Summary: regex: don't deref NULL upon heap allocation failure
           Product: glibc
           Version: 2.21
            Status: NEW
          Severity: normal
          Priority: P2
         Component: regex
          Assignee: unassigned at sourceware dot org
          Reporter: jim at meyering dot net
                CC: drepper.fsp at gmail dot com

Here's the ChangeLog entry for the attached patch:

2014-07-12  Jim Meyering  <meyering@fb.com>

        regex: don't deref NULL upon heap allocation failure
        * posix/regcomp.c (parse_dup_op): Handle duplicate_tree
        failure in one more place.
        To trigger the segfault, configure grep -with-included-regex,
        build it, and run these commands:
        ( ulimit -v 300000; echo a|src/grep -E a+++++++++++++++++++++ )

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


             reply	other threads:[~2014-07-13  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13  0:06 jim at meyering dot net [this message]
2014-07-13  0:09 ` [Bug regex/17150] " jim at meyering dot net
2014-07-14  4:05 ` allan at archlinux dot org
2014-07-23  6:55 ` allan at archlinux dot 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-17150-132@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs-regex@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).