> > >> I'm confused. glibc's rt/tst-cputimer1 doesn't have thread exiting code. I > >> have > >> no seen any issue in this accounting. > > > > glibc launch a helper thread to receive timer signal and will also > > create a new thread upon signal reception when a timer is created with > > sigev_notify = SIGEV_THREAD; > > > > please see: > > > > glibc-2.17/nptl/sysdeps/unix/sysv/linux/timer_create.c > > glibc-2.17/nptl/sysdeps/unix/sysv/linux/timer_routines.c > > I know. I taled thread exiting. not thread creating. And, as far as I can > see, only test sig1 can fail, > not thr[12]. > Apart from glibc helper thread, the threads created for handling timer firing all do exit immediatly as soon as user callback returns.
I count 12 thread exits during tst-cputimer1 execution. The errors do add up hence you're more likely to see errors after 2.5 sec and up from start of execution. I have seen sig1, thr[12] fails. I see no reason why one could not fail. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
