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 malloc/15073] Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption
Date: Sun, 05 Jan 2014 02:05:00 -0000	[thread overview]
Message-ID: <bug-15073-131-bq1KcxTKux@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15073-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15073

--- Comment #12 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, 2.15 has been created
        at  9875bb22212391e39d9d2c29b4b5d5e9e1f83beb (commit)

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9875bb22212391e39d9d2c29b4b5d5e9e1f83beb

commit 9875bb22212391e39d9d2c29b4b5d5e9e1f83beb
Author: Maxim Kuvyrkov <maxim@kugelworks.com>
Date:   Tue Dec 24 09:44:50 2013 +1300

    Fix race in free() of fastbin chunk: BZ #15073

    Perform sanity check only if we have_lock.  Due to lockless nature of
fastbins
    we need to be careful derefencing pointers to fastbin entries
(chunksize(old)
    in this case) in multithreaded environments.

    The fix is to add have_lock to the if-condition checks.  The rest of the
patch
    only makes code more readable.

        * malloc/malloc.c (_int_free): Perform sanity check only if we
        have_lock.

    Conflicts:

        ChangeLog
        NEWS

-----------------------------------------------------------------------

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


  parent reply	other threads:[~2014-01-05  2:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 16:18 [Bug malloc/15073] New: " jpieper at jaybridge dot com
2013-01-28 16:44 ` [Bug malloc/15073] " ngallaher+sources at deepthought dot org
2013-04-16 14:30 ` siddhesh at redhat dot com
2013-04-16 15:56 ` sources at fatlxception dot no-ip.org
2013-05-13  9:23 ` siddhesh at redhat dot com
2013-10-22 19:31 ` nate+sourceware at jaybridge dot com
2013-10-22 21:11 ` nate+sourceware at jaybridge dot com
2013-12-20 22:11 ` carlos at redhat dot com
2013-12-21  0:39 ` neleai at seznam dot cz
2013-12-22 23:38 ` maxim.kuvyrkov at gmail dot com
2013-12-22 23:41 ` maxim.kuvyrkov at gmail dot com
2013-12-23 21:07 ` cvs-commit at gcc dot gnu.org
2013-12-23 21:12 ` maxim.kuvyrkov at gmail dot com
2013-12-27 23:11 ` maxim.kuvyrkov at gmail dot com
2014-01-05  2:05 ` cvs-commit at gcc dot gnu.org [this message]
2014-01-05  2:06 ` cvs-commit at gcc dot gnu.org
2014-01-05  2:16 ` cvs-commit at gcc dot gnu.org
2014-01-05  2:17 ` maxim.kuvyrkov at gmail dot com
2014-01-05  2:18 ` cvs-commit at gcc dot gnu.org
2014-01-05  2:18 ` maxim.kuvyrkov at gmail dot com
2014-01-05  2:18 ` cvs-commit at gcc dot gnu.org
2014-01-05  2:19 ` cvs-commit at gcc dot gnu.org
2014-01-05  2:19 ` maxim.kuvyrkov at gmail dot com
2014-01-05  2:20 ` maxim.kuvyrkov at gmail dot com
2014-06-13 10:11 ` 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-15073-131-bq1KcxTKux@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).