This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: pthread_mutex_unlock potentially cause invalid access

From: Atsushi Nemoto <anemo at mba dot ocn dot ne dot jp>
To: carlos at systemhalted dot org
Cc: kosaki dot motohiro at gmail dot com, libc-alpha at sources dot redhat dot com
Date: Tue, 14 Feb 2012 23:57:01 +0900 (JST)
Subject: Re: pthread_mutex_unlock potentially cause invalid access
References: <CADZpyiy5FGmDhjjeBjY8Br8nKDq6y8N6CJzox-YS4p2Yp9PeDQ@mail.gmail.com><CAHGf_=pjLBoESnQTw+Q9OoEn4r=fHsMinTLdD5aZY_AB=sVF3A@mail.gmail.com><CADZpyiwK4MN2d3Vg=OxZNa88BNtKZfQU8tdugMTy1zzV4m_3CQ@mail.gmail.com>

On Mon, 13 Feb 2012 10:28:49 -0500, "Carlos O'Donell" <carlos@systemhalted.org> wrote:
> Excellent, *this* makes sense and I now agree that there is a problem.
> 
> Nemoto-san could you please file a bug report and tag it with
> glibc_2.15 keyword so I can backport this to 2.15?

Yes, I filed a bug report with the POSIX example and KOSAKI-san's
explanation.

http://sourceware.org/bugzilla/show_activity.cgi?id=13690

---
Atsushi Nemoto

Follow-Ups:
- Re: pthread_mutex_unlock potentially cause invalid access
  - From: Carlos O'Donell

References:
- Re: pthread_mutex_unlock potentially cause invalid access
  - From: Carlos O'Donell
- Re: pthread_mutex_unlock potentially cause invalid access
  - From: KOSAKI Motohiro
- Re: pthread_mutex_unlock potentially cause invalid access
  - From: Carlos O'Donell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]