From bbbe87e35cfeef593e23010e35528e722027567f Mon Sep 17 00:00:00 2001 From: Rich Felker Date: Thu, 12 Jul 2012 11:23:43 -0400 Subject: fix several locks that weren't updated right for new futex-based __lock these could have caused memory corruption due to invalid accesses to the next field. all should be fixed now; I found the errors with fgrep -r '__lock(&', which is bogus since the argument should be an array. --- src/thread/pthread_kill.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/thread/pthread_kill.c') diff --git a/src/thread/pthread_kill.c b/src/thread/pthread_kill.c index 15f70fb9..d9a5096a 100644 --- a/src/thread/pthread_kill.c +++ b/src/thread/pthread_kill.c @@ -3,8 +3,8 @@ int pthread_kill(pthread_t t, int sig) { int r; - __lock(&t->killlock); + __lock(t->killlock); r = t->dead ? ESRCH : -__syscall(SYS_tgkill, t->pid, t->tid, sig); - __unlock(&t->killlock); + __unlock(t->killlock); return r; } -- cgit v1.2.1