From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH][BZ 21357] unwind-dw2-fde: Call free() outside of unwind mutex
Date: Mon, 10 Apr 2017 14:40:00 -0000 [thread overview]
Message-ID: <4a4719c1-1381-fb60-7a06-d1db29b474d2@linaro.org> (raw)
In-Reply-To: <1491508681-30385-1-git-send-email-rabin.vincent@axis.com>
On 06/04/2017 16:58, Rabin Vincent wrote:
> From: Rabin Vincent <rabinv@axis.com>
>
> __deregister_frame_info_bases() calls free() while holding a mutex which
> is also used from _Unwind_Find_FDE(). This leads to a deadlock if
> AddressSanitizer uses _Unwind_Backtrace() from its free()
> implementation.
>
> 2017-04-06 Rabin Vincent <rabinv@axis.com>
>
> [BZ #21357]
> * sysdeps/generic/unwind-dw2-fde.c (__deregister_frame_info_bases):
> Call free() outside of mutex.
>
> diff --git a/sysdeps/generic/unwind-dw2-fde.c b/sysdeps/generic/unwind-dw2-fde.c
> index 2f0bcd2..104a255 100644
> --- a/sysdeps/generic/unwind-dw2-fde.c
> +++ b/sysdeps/generic/unwind-dw2-fde.c
> @@ -202,6 +202,7 @@ __deregister_frame_info_bases (void *begin)
> {
> struct object **p;
> struct object *ob = 0;
> + struct fde_vector *tofree = NULL;
>
> /* If .eh_frame is empty, we haven't registered. */
> if (*(uword *) begin == 0)
> @@ -225,7 +226,7 @@ __deregister_frame_info_bases (void *begin)
> {
> ob = *p;
> *p = ob->next;
> - free (ob->u.sort);
> + tofree = ob->u.sort;
> goto out;
> }
> }
> @@ -244,6 +245,7 @@ __deregister_frame_info_bases (void *begin)
>
> out:
> __gthread_mutex_unlock (&object_mutex);
> + free (tofree);
> return (void *) ob;
> }
> hidden_def (__deregister_frame_info_bases)
LGTM, I assume you actually tested on some platform, right? Do you have write access?
next prev parent reply other threads:[~2017-04-10 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 19:58 Rabin Vincent
2017-04-10 14:40 ` Adhemerval Zanella [this message]
2017-04-13 9:55 ` Rabin Vincent
2017-04-13 17:28 ` Adhemerval Zanella
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=4a4719c1-1381-fb60-7a06-d1db29b474d2@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@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).