Thread-related LOR in exit1() (fwd)
David Xu
davidxu at freebsd.org
Mon Apr 21 07:57:22 PDT 2003
----- Original Message -----
From: "Daniel Eischen" <eischen at pcnet1.pcnet.com>
To: <threads at freebsd.org>
Cc: <davidxu at freebsd.org>
Sent: Monday, April 21, 2003 10:33 PM
Subject: Thread-related LOR in exit1() (fwd)
> David, did you see this message sent to -current?
>
I have committed a fix.
> Also, I have scope system threads running in a simple test. I'm
> getting EPROCLIM though when trying to create more than 4 or so
> of them (KSEs with their own KSEG).
>
Yeah, sysctl -a |grep kern.threads
should show the reason, please increase max_groups_per_proc sysctl by hand,
I know it's too small. :-)
> Here's the patches to libpthread that I'm currently using along
> with a test program.
>
> http://people.freebsd.org/~deischen/kse/libpthread.diffs
> http://people.freebsd.org/~deischen/kse/thread_test2.c
>
I am going to sleep again, I will test it tomorrow.
it seems KMF_NOCOMPLETED should be added in _kse_lock_wait().
> --
> Dan
>
> ---------- Forwarded message ----------
> Date: Mon, 21 Apr 2003 20:25:41 +1000
> From: Tim Robbins <tjr at freebsd.org>
> To: current at freebsd.org
> Subject: Thread-related LOR in exit1()
>
> While running a trivial test program linked with libkse that created
> 3 threads:
>
> lock order reversal
> 1st 0xc0f0f428 process lock (process lock) @ /usr/src/sys/kern/kern_exit.c:134
> 2nd 0xc02f75c0 Giant (Giant) @ /usr/src/sys/kern/kern_exit.c:142
>
>
> Tim
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>
> _______________________________________________
> freebsd-threads at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-threads
> To unsubscribe, send any mail to "freebsd-threads-unsubscribe at freebsd.org"
More information about the freebsd-threads
mailing list