miscellaneous interrupted system call.

[Dirk Morris]

I'm getting random threads woken up when other threads make a 
system("foo") call.

I've been having the sympton since the 2.5 series.
It does not happen in the 2.4 series.
I thought it was somehow related to the futex_badness, but now I think 
it may be some libc NPTL issue.

Any ideas?

Sample program:
/* $Id: foo.c,v 1.00 2004/03/31 10:51:19 dmorris Exp $ */
/* gcc foo.c -o foo -pthread */
#include <stdlib.h>
#include <stdio.h>
#include <unistd.h>
#include <pthread.h>
#include <semaphore.h>

sem_t sem;

void* make_system_call (void* arg)
{
  while(1) {
      sleep(1);
      system("/bin/true");
  }
  return NULL;
}

int main(void)
{
  pthread_t id;
  sem_init(&sem,0,0);
  pthread_create(&id,NULL,make_system_call,NULL);
  while (sem_wait(&sem)<0)
      perror("sem_wait");
  return 0;
}

Output:
~/misc # ./foo 
                                                                               

sem_wait: Interrupted system call
sem_wait: Interrupted system call
...

Machine info:
It happens on all my 2.5/2.6 machines, all running debian 
testing/unstable in some flavor.
Here's one example:

~/misc # uname 
-a                                                                                     

Linux bebe 2.6.8.1 #2 SMP Fri Aug 20 13:32:31 PDT 2004 i686 GNU/Linux
~/misc # gcc 
-v                                                                                     

Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.4/specs
Configured with: ../src/configure -v 
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr 
--mandir=/usr/share/man --infodir=/usr/share/info 
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared 
--with-system-zlib --enable-nls --without-included-gettext 
--enable-__cxa_atexit --enable-clocale=gnu --enable-debug 
--enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i486-linux
Thread model: posix
gcc version 3.3.4 (Debian 1:3.3.4-6sarge1)


Thanks,

-Dirk


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/