From owner-freebsd-hackers@FreeBSD.ORG Fri May 6 09:12:00 2011 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDE19106564A for ; Fri, 6 May 2011 09:12:00 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E00F18FC08 for ; Fri, 6 May 2011 09:11:59 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA21450 for ; Fri, 06 May 2011 12:11:58 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QIH4o-000D20-EF for hackers@freebsd.org; Fri, 06 May 2011 12:11:58 +0300 Message-ID: <4DC3BB5D.5080300@FreeBSD.org> Date: Fri, 06 May 2011 12:11:57 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: hackers@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: Subject: thread_lock vs panic/trap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2011 09:12:00 -0000 Can a current thread panic or receive a trap while some other thread holds its thread_lock (the same lock as pointed to by the td_lock)? And a related question, can there be a reason for a thread in panic or kdb context to try to get the thread_lock? Thank you! -- Andriy Gapon