Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 07 Aug 2014 00:43:35 +0200
From: Jens Gustedt <>
Subject: Re: Explaining cond var destroy [Re: C threads, v3.0]

Am Mittwoch, den 06.08.2014, 18:04 -0400 schrieb Rich Felker:
> No. The problem is that the memory in which the cond var resides could
> previously have been used for a mutex, semaphore, or other object for
> which a futex wait arrives "very late" due to scheduling. It has
> nothing to do with the destruction of cond vars.

Hm, but then we have a problem on the side that has this late wait,
that is an access to a dead object. So the UB is there, in that thread
that is doing the wait. (Suppose it is just threads and not processes,
that would even be more complicated.) That spurious wakeup that you
are talking about is a consequence of UB.

good night


:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: ::

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.