public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@hack.frob.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: libc-alpha@sourceware.org,    libc-ports@sourceware.org
Subject: Re: pthread_mutex_unlock potentially cause invalid access
Date: Fri, 10 Feb 2012 21:16:00 -0000	[thread overview]
Message-ID: <20120210211642.7DF022C069@topped-with-meat.com> (raw)
In-Reply-To: Atsushi Nemoto's message of  Friday, 10 February 2012 23:43:26 +0900 <20120210.234326.199788933.anemo@mba.ocn.ne.jp>

> Possible fix would be copying the 'private' argument to an internal
> local variable before atomic_exchange_rel().  Is it an appropriate fix?

That seems right to me off hand.  But I'm not really the expert on the
subtleties of this code.


Thanks,
Roland

  reply	other threads:[~2012-02-10 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 14:43 Atsushi Nemoto
2012-02-10 21:16 ` Roland McGrath [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-10 14:28 Atsushi Nemoto

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=20120210211642.7DF022C069@topped-with-meat.com \
    --to=roland@hack.frob.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@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).