This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

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: [PATCH] Fix linuxthreads with pthread_attr_setstack{,addr}

From: Jakub Jelinek <jakub at redhat dot com>
To: Ulrich Drepper <drepper at redhat dot com>
Cc: Glibc hackers <libc-hacker at sources dot redhat dot com>, hjl at lucon dot org
Date: Thu, 29 Apr 2004 16:31:30 +0200
Subject: Re: [PATCH] Fix linuxthreads with pthread_attr_setstack{,addr}
References: <20040429141901.GR5191@sunsite.ms.mff.cuni.cz>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Thu, Apr 29, 2004 at 04:19:02PM +0200, Jakub Jelinek wrote:
> Hi!
> 
> Despite what the bugzilla says, I believe the problem is not related
> to TLS.  After pthread_join successfully returns, the user thread stack
> may be still in use (both by the thread manager (thread descriptor,
> i.e. !TLS only) and by the actual thread being joined (both the thread
> descriptor and stack being in use)).
> The following patch for p_userstack threads waits in pthread_join
> till thread manager tells it will not use the thread stack any longer.

POSIX says on pthread_join:

"For instance, after pthread_join() returns, any application-provided stack storage
 could be reclaimed."

so I guess we need to support that.

	Jakub

Follow-Ups:
- Re: [PATCH] Fix linuxthreads with pthread_attr_setstack{,addr}
  - From: Wolfram Gloger

References:
- [PATCH] Fix linuxthreads with pthread_attr_setstack{,addr}
  - From: Jakub Jelinek

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