From owner-freebsd-current Thu Nov 14 5: 9:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AB0237B401 for ; Thu, 14 Nov 2002 05:09:09 -0800 (PST) Received: from smtp01.iprimus.net.au (smtp01.iprimus.net.au [210.50.30.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ED1A43E4A for ; Thu, 14 Nov 2002 05:09:08 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au ([210.50.114.183]) by smtp01.iprimus.net.au with Microsoft SMTPSVC(5.0.2195.5600); Fri, 15 Nov 2002 00:08:31 +1100 Received: from dilbert.robbins.dropbear.id.au (ba27e6mvibqk0gbr@localhost [127.0.0.1]) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6) with ESMTP id gAED7Ibo047372 for ; Fri, 15 Nov 2002 00:07:39 +1100 (EST) (envelope-from tim@dilbert.robbins.dropbear.id.au) Received: (from tim@localhost) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6/Submit) id gAED6qV3047344 for current@FreeBSD.org; Fri, 15 Nov 2002 00:06:52 +1100 (EST) (envelope-from tim) Date: Fri, 15 Nov 2002 00:06:51 +1100 From: Tim Robbins To: current@FreeBSD.org Subject: truss and KSE Message-ID: <20021115000651.A46903@dilbert.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-OriginalArrivalTime: 14 Nov 2002 13:08:55.0728 (UTC) FILETIME=[FCA22300:01C28BDE] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While experimenting with the new libpthread, I found that if you run `truss' on a KSE process, both truss and its victim get into a weird state and don't respond to TERM, INT or QUIT signals. The truss proc dies if you send it the KILL signal, but the victim process cannot be killed. Stranger still, it's in the run state but not actually performing any work. I understand that KSE is still an experimental feature but I thought this was worth pointing out because it could be used as a local DoS and we are nearing 5.0-RELEASE. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message