From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 02:35:28 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E65E31065673 for ; Mon, 9 Mar 2009 02:35:28 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BA9268FC0C; Mon, 9 Mar 2009 02:35:28 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from apple.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n292ZQtP062061; Mon, 9 Mar 2009 02:35:27 GMT (envelope-from davidxu@freebsd.org) Message-ID: <49B480F7.8040800@freebsd.org> Date: Mon, 09 Mar 2009 10:37:43 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20080612) MIME-Version: 1.0 To: Pawel Worach References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: threads@freebsd.org Subject: Re: libthr does not obey WITHOUT_SYSCALL_COMPAT X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 02:35:29 -0000 Pawel Worach wrote: > Hi, > > If libc is built using WITHOUT_SYSCALL_COMPAT applications linked with > libthr end up having unresolved symbols since libthr references > __fcntl_compat unconditionally. > Here is a patch to make libthr also obey WITHOUT_SYSCALL_COMPAT > http://www.vlakno.cz/~pwo/libthr.diff > > Regards Committed! Thanks, David Xu From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 04:28:20 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D874E106564A; Mon, 9 Mar 2009 04:28:20 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 95F608FC17; Mon, 9 Mar 2009 04:28:20 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n2941IYh022532; Mon, 9 Mar 2009 00:01:18 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 09 Mar 2009 00:01:19 -0400 (EDT) Date: Mon, 9 Mar 2009 00:01:18 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Xu In-Reply-To: <49B480F7.8040800@freebsd.org> Message-ID: References: <49B480F7.8040800@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: threads@freebsd.org, Pawel Worach Subject: Re: libthr does not obey WITHOUT_SYSCALL_COMPAT X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 04:28:21 -0000 On Mon, 9 Mar 2009, David Xu wrote: > Pawel Worach wrote: >> Hi, >> >> If libc is built using WITHOUT_SYSCALL_COMPAT applications linked with >> libthr end up having unresolved symbols since libthr references >> __fcntl_compat unconditionally. >> Here is a patch to make libthr also obey WITHOUT_SYSCALL_COMPAT >> http://www.vlakno.cz/~pwo/libthr.diff >> >> Regards > > Committed! I never got around to replying to this... I don't quite understand why __fcntl_compat is there. We have F_GETFD, F_SETFD, F_DUPFD, F_DUP2FD, F_GETFL, F_SETFL, F_GETOWN, and F_SETOWN according to fcntl(2). But thr_syscalls.c only handles F_DUPFD, F_SETFD, F_SETFL, F_GETFD, and F_GETFL, leaving F_DUP2FD, F_GETOWN, and F_SETOWN to be handled by the default case. And the default case does nothing now if WITHOUT_SYSCALL_COMPAT is defined. So how do F_DUP2FD, F_GETOWN, and F_SETOWN get handled? Do we really need to call __sys_fcntl_compat() from libthr? When did the ABI change, before or after libc.so.7? -- DE From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 05:11:05 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F014A1065674; Mon, 9 Mar 2009 05:11:05 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DC9878FC0C; Mon, 9 Mar 2009 05:11:05 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from apple.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n295B4mK065635; Mon, 9 Mar 2009 05:11:04 GMT (envelope-from davidxu@freebsd.org) Message-ID: <49B4A571.7000302@freebsd.org> Date: Mon, 09 Mar 2009 13:13:21 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20080612) MIME-Version: 1.0 To: Daniel Eischen References: <49B480F7.8040800@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: threads@freebsd.org, Pawel Worach Subject: Re: libthr does not obey WITHOUT_SYSCALL_COMPAT X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 05:11:06 -0000 Daniel Eischen wrote: > On Mon, 9 Mar 2009, David Xu wrote: > >> Pawel Worach wrote: >>> Hi, >>> >>> If libc is built using WITHOUT_SYSCALL_COMPAT applications linked with >>> libthr end up having unresolved symbols since libthr references >>> __fcntl_compat unconditionally. >>> Here is a patch to make libthr also obey WITHOUT_SYSCALL_COMPAT >>> http://www.vlakno.cz/~pwo/libthr.diff >>> >>> Regards >> >> Committed! > > I never got around to replying to this... > > I don't quite understand why __fcntl_compat is there. We have > F_GETFD, F_SETFD, F_DUPFD, F_DUP2FD, F_GETFL, F_SETFL, F_GETOWN, > and F_SETOWN according to fcntl(2). But thr_syscalls.c only > handles F_DUPFD, F_SETFD, F_SETFL, F_GETFD, and F_GETFL, leaving > F_DUP2FD, F_GETOWN, and F_SETOWN to be handled by the default > case. And the default case does nothing now if WITHOUT_SYSCALL_COMPAT > is defined. So how do F_DUP2FD, F_GETOWN, and F_SETOWN get > handled? > > Do we really need to call __sys_fcntl_compat() from libthr? > When did the ABI change, before or after libc.so.7? > I don't know when it appeared. Would this patch eliminate the shit ? Index: thr_syscalls.c =================================================================== --- thr_syscalls.c (revision 189549) +++ thr_syscalls.c (working copy) @@ -258,7 +258,7 @@ #ifdef SYSCALL_COMPAT ret = __fcntl_compat(fd, cmd, va_arg(ap, void *)); #else - ret = EOPNOTSUPP; + ret = __sys_fcntl(fd, cmd, va_arg(ap, void *)); #endif } va_end(ap); From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 05:23:24 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD97610656BA; Mon, 9 Mar 2009 05:23:24 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6A9C58FC5F; Mon, 9 Mar 2009 05:23:24 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n295NNkn008776; Mon, 9 Mar 2009 01:23:23 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 09 Mar 2009 01:23:23 -0400 (EDT) Date: Mon, 9 Mar 2009 01:23:23 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Xu In-Reply-To: <49B4A571.7000302@freebsd.org> Message-ID: References: <49B480F7.8040800@freebsd.org> <49B4A571.7000302@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: threads@freebsd.org, Pawel Worach Subject: Re: libthr does not obey WITHOUT_SYSCALL_COMPAT X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 05:23:25 -0000 On Mon, 9 Mar 2009, David Xu wrote: > Daniel Eischen wrote: >> On Mon, 9 Mar 2009, David Xu wrote: >> >>> Pawel Worach wrote: >>>> Hi, >>>> >>>> If libc is built using WITHOUT_SYSCALL_COMPAT applications linked with >>>> libthr end up having unresolved symbols since libthr references >>>> __fcntl_compat unconditionally. >>>> Here is a patch to make libthr also obey WITHOUT_SYSCALL_COMPAT >>>> http://www.vlakno.cz/~pwo/libthr.diff >>>> >>>> Regards >>> >>> Committed! >> >> I never got around to replying to this... >> >> I don't quite understand why __fcntl_compat is there. We have >> F_GETFD, F_SETFD, F_DUPFD, F_DUP2FD, F_GETFL, F_SETFL, F_GETOWN, >> and F_SETOWN according to fcntl(2). But thr_syscalls.c only >> handles F_DUPFD, F_SETFD, F_SETFL, F_GETFD, and F_GETFL, leaving >> F_DUP2FD, F_GETOWN, and F_SETOWN to be handled by the default >> case. And the default case does nothing now if WITHOUT_SYSCALL_COMPAT >> is defined. So how do F_DUP2FD, F_GETOWN, and F_SETOWN get >> handled? >> >> Do we really need to call __sys_fcntl_compat() from libthr? >> When did the ABI change, before or after libc.so.7? >> > > I don't know when it appeared. Would this patch eliminate the shit ? I think so. But I think for future ABI changes to cancellation points, wouldn't we need syscall wrappers in libc? Reason, libc and libthr are now symbol-versioned, so there will no longer be library bumps for ABI changes. But if a syscall is a cancellation point and libthr has to play games with it, like fcntl, I think there should be a wrapper around it in libc. If the ABI changes, then both libc and libthr would need to provide a compat version for it. I think. ;-) -- DE From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 06:00:08 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C4C01065672; Mon, 9 Mar 2009 06:00:08 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D189E8FC17; Mon, 9 Mar 2009 06:00:07 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from apple.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n29606Zg025015; Mon, 9 Mar 2009 06:00:07 GMT (envelope-from davidxu@freebsd.org) Message-ID: <49B4B0EF.5080507@freebsd.org> Date: Mon, 09 Mar 2009 14:02:23 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20080612) MIME-Version: 1.0 To: Daniel Eischen References: <49B480F7.8040800@freebsd.org> <49B4A571.7000302@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: threads@freebsd.org, Pawel Worach Subject: Re: libthr does not obey WITHOUT_SYSCALL_COMPAT X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 06:00:08 -0000 Daniel Eischen wrote: > On Mon, 9 Mar 2009, David Xu wrote: > >> Daniel Eischen wrote: >>> On Mon, 9 Mar 2009, David Xu wrote: >>> >>>> Pawel Worach wrote: >>>>> Hi, >>>>> >>>>> If libc is built using WITHOUT_SYSCALL_COMPAT applications linked with >>>>> libthr end up having unresolved symbols since libthr references >>>>> __fcntl_compat unconditionally. >>>>> Here is a patch to make libthr also obey WITHOUT_SYSCALL_COMPAT >>>>> http://www.vlakno.cz/~pwo/libthr.diff >>>>> >>>>> Regards >>>> >>>> Committed! >>> >>> I never got around to replying to this... >>> >>> I don't quite understand why __fcntl_compat is there. We have >>> F_GETFD, F_SETFD, F_DUPFD, F_DUP2FD, F_GETFL, F_SETFL, F_GETOWN, >>> and F_SETOWN according to fcntl(2). But thr_syscalls.c only >>> handles F_DUPFD, F_SETFD, F_SETFL, F_GETFD, and F_GETFL, leaving >>> F_DUP2FD, F_GETOWN, and F_SETOWN to be handled by the default >>> case. And the default case does nothing now if WITHOUT_SYSCALL_COMPAT >>> is defined. So how do F_DUP2FD, F_GETOWN, and F_SETOWN get >>> handled? >>> >>> Do we really need to call __sys_fcntl_compat() from libthr? >>> When did the ABI change, before or after libc.so.7? >>> >> >> I don't know when it appeared. Would this patch eliminate the shit ? > > I think so. But I think for future ABI changes to cancellation > points, wouldn't we need syscall wrappers in libc? Reason, libc > and libthr are now symbol-versioned, so there will no longer be > library bumps for ABI changes. But if a syscall is a cancellation > point and libthr has to play games with it, like fcntl, I think > there should be a wrapper around it in libc. If the ABI changes, > then both libc and libthr would need to provide a compat version > for it. I think. ;-) > Yes, it is better to use versioning instead, I don't know why fcntl_compat is there without using this feature. From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 12:00:26 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DA1A10658F3; Mon, 9 Mar 2009 12:00:25 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 70F3F8FC16; Mon, 9 Mar 2009 12:00:25 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n29C0OFp016171; Mon, 9 Mar 2009 08:00:24 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 09 Mar 2009 08:00:24 -0400 (EDT) Date: Mon, 9 Mar 2009 08:00:24 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Xu In-Reply-To: <49B4B0EF.5080507@freebsd.org> Message-ID: References: <49B480F7.8040800@freebsd.org> <49B4A571.7000302@freebsd.org> <49B4B0EF.5080507@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: threads@freebsd.org, Pawel Worach Subject: Re: libthr does not obey WITHOUT_SYSCALL_COMPAT X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 12:00:27 -0000 On Mon, 9 Mar 2009, David Xu wrote: > Daniel Eischen wrote: >> On Mon, 9 Mar 2009, David Xu wrote: >> >>> I don't know when it appeared. Would this patch eliminate the shit ? >> >> I think so. But I think for future ABI changes to cancellation >> points, wouldn't we need syscall wrappers in libc? Reason, libc >> and libthr are now symbol-versioned, so there will no longer be >> library bumps for ABI changes. But if a syscall is a cancellation >> point and libthr has to play games with it, like fcntl, I think >> there should be a wrapper around it in libc. If the ABI changes, >> then both libc and libthr would need to provide a compat version >> for it. I think. ;-) >> > > Yes, it is better to use versioning instead, I don't know why fcntl_compat is > there without using this feature. Hmm, looking a little closer at this... It looks like there is a wrapper for fcntl in libc (libc/sys/fcntl.c). But I think it should always be built. Currently, it is hidden behind WITHOUT_SYSCALL_COMPAT in libc/sys/Makefile. But it never calls an older fcntl syscall. It just transforms the old style struct into new style, then calls the new fcntl syscall. So I think the mistake is building fcntl.c conditionally, when it should always be built regardless of WITHOUT_SYSCALL_COMPAT being defined or not defined. -- DE From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 12:15:18 2009 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2EA2106564A; Mon, 9 Mar 2009 12:15:18 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 576A38FC16; Mon, 9 Mar 2009 12:15:18 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n29CFGOZ022847; Mon, 9 Mar 2009 08:15:16 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 09 Mar 2009 08:15:16 -0400 (EDT) Date: Mon, 9 Mar 2009 08:15:16 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Xu In-Reply-To: Message-ID: References: <49B480F7.8040800@freebsd.org> <49B4A571.7000302@freebsd.org> <49B4B0EF.5080507@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: threads@freebsd.org, Pawel Worach Subject: Re: libthr does not obey WITHOUT_SYSCALL_COMPAT X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 12:15:19 -0000 On Mon, 9 Mar 2009, Daniel Eischen wrote: > On Mon, 9 Mar 2009, David Xu wrote: > >> Daniel Eischen wrote: >>> On Mon, 9 Mar 2009, David Xu wrote: >>> >>>> I don't know when it appeared. Would this patch eliminate the shit ? >>> >>> I think so. But I think for future ABI changes to cancellation >>> points, wouldn't we need syscall wrappers in libc? Reason, libc >>> and libthr are now symbol-versioned, so there will no longer be >>> library bumps for ABI changes. But if a syscall is a cancellation >>> point and libthr has to play games with it, like fcntl, I think >>> there should be a wrapper around it in libc. If the ABI changes, >>> then both libc and libthr would need to provide a compat version >>> for it. I think. ;-) >>> >> >> Yes, it is better to use versioning instead, I don't know why fcntl_compat >> is there without using this feature. > > Hmm, looking a little closer at this... It looks like there > is a wrapper for fcntl in libc (libc/sys/fcntl.c). But I think > it should always be built. Currently, it is hidden behind > WITHOUT_SYSCALL_COMPAT in libc/sys/Makefile. But it never calls > an older fcntl syscall. It just transforms the old style struct ^^^ new > into new style, then calls the new fcntl syscall. ^^^ old > So I think the mistake is building fcntl.c conditionally, when > it should always be built regardless of WITHOUT_SYSCALL_COMPAT > being defined or not defined. I guess if the default is with syscall compat, then it is okay to build optionally without it. -- DE From owner-freebsd-threads@FreeBSD.ORG Mon Mar 9 17:15:14 2009 Return-Path: Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54F8B10656EA for ; Mon, 9 Mar 2009 17:15:14 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3558E8FC18 for ; Mon, 9 Mar 2009 17:15:14 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n29HFECe045418 for ; Mon, 9 Mar 2009 17:15:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n29HFDOB045414 for freebsd-threads@FreeBSD.org; Mon, 9 Mar 2009 17:15:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Mar 2009 17:15:13 GMT Message-Id: <200903091715.n29HFDOB045414@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-threads@FreeBSD.org X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 17:15:19 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o threa/128922 threads threads hang with xorg running o threa/127225 threads bug in lib/libthr/thread/thr_init.c o threa/122923 threads 'nice' does not prevent background process from steali o threa/121336 threads lang/neko threading ok on UP, broken on SMP (FreeBSD 7 o threa/118715 threads kse problem o threa/116668 threads can no longer use jdk15 with libthr on -stable SMP o threa/116181 threads /dev/io-related io access permissions are not propagat o threa/115211 threads pthread_atfork misbehaves in initial thread o threa/110636 threads [request] gdb(1): using gdb with multi thread applicat o threa/110306 threads apache 2.0 segmentation violation when calling gethost o threa/103975 threads Implicit loading/unloading of libpthread.so may crash o threa/101323 threads [patch] fork(2) in threaded programs broken. s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc s threa/84483 threads problems with devel/nspr and -lc_r on 4.x o threa/83914 threads [libc] popen() doesn't work in static threaded program o threa/80992 threads abort() sometimes not caught by gdb depending on threa o threa/80435 threads panic on high loads o threa/79887 threads [patch] freopen() isn't thread-safe o threa/79683 threads svctcp_create() fails if multiple threads call at the s threa/76694 threads fork cause hang in dup()/close() function in child (-l s threa/76690 threads fork hang in child for -lc_r o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag o threa/75273 threads FBSD 5.3 libpthread (KSE) bug o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST o threa/70975 threads [sysvipc] unexpected and unreliable behaviour when usi s threa/69020 threads pthreads library leaks _gc_mutex s threa/49087 threads Signals lost in programs linked with libc_r s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under s threa/40671 threads pthread_cancel doesn't remove thread from condition qu s threa/39922 threads [threads] [patch] Threaded applications executed with s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra s threa/34536 threads accept() blocks other threads s threa/32295 threads [libc_r] [patch] pthread(3) dont dequeue signals s threa/30464 threads pthread mutex attributes -- pshared s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o 37 problems total.