From owner-freebsd-threads@FreeBSD.ORG Mon Dec 22 11:03:03 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF1E116A4CF for ; Mon, 22 Dec 2003 11:03:03 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FE8443D96 for ; Mon, 22 Dec 2003 11:01:47 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) hBMJ1WFR067490 for ; Mon, 22 Dec 2003 11:01:32 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id hBMJ1Vjr067485 for freebsd-threads@freebsd.org; Mon, 22 Dec 2003 11:01:31 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 22 Dec 2003 11:01:31 -0800 (PST) Message-Id: <200312221901.hBMJ1Vjr067485@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 19:03:03 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything o [2002/01/16] kern/33951 threads pthread_cancel is ignored 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/07/18] kern/20016 threads pthreads: Cannot set scheduling timer/Can o [2000/08/26] misc/20861 threads libc_r does not honor socket timeouts o [2001/01/19] bin/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] bin/24632 threads libc_r delicate deviation from libc in ha o [2001/01/25] misc/24641 threads pthread_rwlock_rdlock can deadlock o [2001/04/02] bin/26307 threads libc_r aborts when using the KDE media pl o [2001/10/31] bin/31661 threads pthread_kill signal handler doesn't get s o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/02/01] i386/34536 threads accept() blocks other threads o [2002/03/07] bin/35622 threads sigaltstack is missing in libc_r o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/06/27] bin/39922 threads [PATCH?] Threaded applications executed w o [2002/08/04] misc/41331 threads Pthread library open sets O_NONBLOCK flag o [2002/10/10] kern/43887 threads abnormal CPU useage when use pthread_mute o [2003/03/02] bin/48856 threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] bin/49087 threads Signals lost in programs linked with libc a [2003/04/08] bin/50733 threads buildworld won't build, because of linkin o [2003/05/07] bin/51949 threads thread in accept cannot be cancelled o [2003/05/30] kern/52817 threads top(1) shows garbage for threaded process 19 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/05/25] misc/18824 threads gethostbyname is not thread safe o [2000/10/21] misc/22190 threads A threaded read(2) from a socketpair(2) f o [2001/09/09] bin/30464 threads pthread mutex attributes -- pshared o [2002/05/02] bin/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwri o [2002/07/16] misc/40671 threads pthread_cancel doesn't remove thread from 5 problems total. From owner-freebsd-threads@FreeBSD.ORG Thu Dec 25 01:49:33 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28DE216A4CE for ; Thu, 25 Dec 2003 01:49:33 -0800 (PST) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37C0643D53 for ; Thu, 25 Dec 2003 01:49:31 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (localhost [127.0.0.1]) by silver.he.iki.fi (8.12.9p2/8.11.4) with ESMTP id hBP9nSgr030139 for ; Thu, 25 Dec 2003 11:49:29 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <3FEAB27E.90306@he.iki.fi> Date: Thu, 25 Dec 2003 11:48:46 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: mysql support with kse X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Dec 2003 09:49:33 -0000 Is Mysql server supposed to work with libkse? I have world from 9 Dec and kernel from 8 Dec and mysql works but mysqladmin cannot for example shutdown the server but has no effect. Pete From owner-freebsd-threads@FreeBSD.ORG Thu Dec 25 07:59:23 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E05516A4CF for ; Thu, 25 Dec 2003 07:59:23 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A1E743D1D for ; Thu, 25 Dec 2003 07:59:22 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id hBPFwYUd078860 for ; Thu, 25 Dec 2003 10:58:34 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hBPFwYor078857 for ; Thu, 25 Dec 2003 10:58:34 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 25 Dec 2003 10:58:34 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: threads@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: file descriptor leak in 5.2-RC (fwd) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Dec 2003 15:59:23 -0000 I'm sure you guys have picked up on this already, but there have been a number of reports of file descriptor leakage on the -current mailing list. In the past 24 hours, I've heard back from several of the people involved with essentially the same message as below: the leaks occur when using libkse, but not libc_r. Unfortunately, it doesn't sound like it's been narrowed down to a single application, but I wonder if there's a race/reference counting problem in process shutdown when running with multiple KSE's... Anyhow, just a heads up. thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research ---------- Forwarded message ---------- Date: Thu, 25 Dec 2003 02:36:49 +0100 (CET) From: Michal Mertl To: freebsd-current@freebsd.org Subject: Re: file descriptor leak in 5.2-RC I found out that the leak doesn't occur in my environment if I change threading library back to libc_r. -- Michal Mertl _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-threads@FreeBSD.ORG Fri Dec 26 03:39:09 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D54916A4CE for ; Fri, 26 Dec 2003 03:39:09 -0800 (PST) Received: from telecom.net.et (ns2.telecom.net.et [213.55.64.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8992343D46 for ; Fri, 26 Dec 2003 03:39:04 -0800 (PST) (envelope-from mtm@identd.net) Received: from [213.55.65.148] (HELO pool-151-200-10-97.res.east.verizon.net) by telecom.net.et (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 32765317; Fri, 26 Dec 2003 14:33:39 +0300 Received: from mobile.acsolutions.com (localhost [127.0.0.1]) ESMTP id hBQBbT2Y000993; Fri, 26 Dec 2003 14:38:00 +0300 (EAT) (envelope-from mtm@mobile.acsolutions.com) Received: (from mtm@localhost) by mobile.acsolutions.com (8.12.10/8.12.10/Submit) id hBQ9i8on008743; Fri, 26 Dec 2003 12:44:08 +0300 (EAT) (envelope-from mtm) Date: Fri, 26 Dec 2003 12:44:08 +0300 From: Mike Makonnen To: Doug Rabson Message-ID: <20031226094408.GA8712@mobile.acsolutions.com> References: <1066052677.14360.29.camel@builder02.qubesoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1066052677.14360.29.camel@builder02.qubesoft.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD/5.2-CURRENT (i386) cc: threads@freebsd.org Subject: Re: GDB and libthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Dec 2003 11:39:09 -0000 On Mon, Oct 13, 2003 at 02:44:37PM +0100, Doug Rabson wrote: > I just upgraded one of my systems to the latest current and I came > across some problems with libthr. A program which I was working on > suddenly found itself linked against libthr (presumably because of a new > version of libmap.conf or similar) and I found myself completely unable > to debug it. This was not a threaded application, merely one which had > linked against libthr. > > The symtoms are that when running the application under gdb, it quickly > hangs and starts consuming as much CPU time as it can. I looked into > things carefully and at the bottom of things, I discovered that when a > libthr mutex is held, the process blocks out SIGTRAP (among other > things). If the application hits a breakpoint while the mutex is held, > everything quickly goes pear shaped since the application doesn't get > the SIGTRAP. Basically it gets into a tight loop of hitting the > breakpoint, getting a signal, ignoring it and then trying to execute the > breakpoint instruction again. > > Since this also happens when dlopen is called (there is always a > breakpoint inside the dynamic linker to keep GDB's list of shared > libraries up to date) and since comon apis such as getpwuid end up in > dlopen via nsdispatch, it becomes impossible to run many applications > even without setting breakpoints. Also, if an application happens to > take a non-recoverable fatal signal such as SIGSEGV, SIGBUS, SIGSYS or > similar while holding a mutex, it will wedge itself in a tight loop in a > similar way, whether or not it is running under GDB. > > The simplest change which fixed things for me was to remove SIGTRAP from > the list of signals blocked on mutex entry. This does not fix the > similar problems with SIGSEGV etc. > Sorry for getting back to you so late, but I was away for a while, and it's taking some time to catch up with mail :(. Yes, you're right: the list of caught and blocked signals in libthr needs to be revised and fixed. It's on the *big* list of TODOs for libthr :-) Feel free to commit the patch, and I'll take a look at revising the status of the rest of the signals. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | Fingerprint: 00E8 61BC 0D75 7FFB E4D3 6BF1 B239 D010 3215 D418 mtm@FreeBSD.Org| FreeBSD - Unleash the Daemon ! From owner-freebsd-threads@FreeBSD.ORG Fri Dec 26 04:35:29 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41EB316A4CE for ; Fri, 26 Dec 2003 04:35:29 -0800 (PST) Received: from herring.nlsystems.com (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96AEA43D1D for ; Fri, 26 Dec 2003 04:35:27 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [10.0.0.2] (herring.nlsystems.com [10.0.0.2]) hBQCZF3k013867; Fri, 26 Dec 2003 12:35:15 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Mike Makonnen In-Reply-To: <20031226094408.GA8712@mobile.acsolutions.com> References: <1066052677.14360.29.camel@builder02.qubesoft.com> <20031226094408.GA8712@mobile.acsolutions.com> Content-Type: text/plain Message-Id: <1072442115.11617.0.camel@herring.nlsystems.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 26 Dec 2003 12:35:15 +0000 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on herring.nlsystems.com cc: threads@freebsd.org Subject: Re: GDB and libthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Dec 2003 12:35:29 -0000 On Fri, 2003-12-26 at 09:44, Mike Makonnen wrote: > > Sorry for getting back to you so late, but I was away for a while, and it's > taking some time to catch up with mail :(. > > Yes, you're right: the list of caught and blocked signals in libthr needs to be > revised and fixed. It's on the *big* list of TODOs for libthr :-) > > Feel free to commit the patch, and I'll take a look at revising the status > of the rest of the signals. No problem - I'd forgotten about it. I've just committed the patch.