This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/13002] robust mutex deadlocks instead of returning EOWNERDEAD
- From: "wang.deqiang1 at zte dot com.cn" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Wed, 10 Aug 2011 04:38:52 +0000
- Subject: [Bug nptl/13002] robust mutex deadlocks instead of returning EOWNERDEAD
- Auto-submitted: auto-generated
- References: <bug-13002-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13002
wangdeqiang <wang.deqiang1 at zte dot com.cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wang.deqiang1 at zte dot
| |com.cn
--- Comment #3 from wangdeqiang <wang.deqiang1 at zte dot com.cn> 2011-08-10 04:38:47 UTC ---
just only do setrobust syscall in child after fork?
if the father is a muti-thread process, when one thread is in fork, the others
might be call pthread_mutex_lock, so the robust list of father(user space) is
not null, when fork is done, there will be some mutex (actually is not owned by
child) in the child's robust_list.
i think the mutex in robust list should be clear in child.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.