From owner-svn-src-head@FreeBSD.ORG Tue Jun 9 10:23:35 2015 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 91DA6FF5; Tue, 9 Jun 2015 10:23:35 +0000 (UTC) (envelope-from br@bsdpad.com) Received: from bsdpad.com (xc1.bsdpad.com [195.154.136.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56B251F9A; Tue, 9 Jun 2015 10:23:34 +0000 (UTC) (envelope-from br@bsdpad.com) Received: from localhost ([127.0.0.1] helo=bsdpad.com) by bsdpad.com with smtp (Exim 4.83 (FreeBSD)) (envelope-from ) id 1Z2GZm-000CG9-6R; Tue, 09 Jun 2015 11:16:10 +0100 Received: by bsdpad.com (nbSMTP-1.00) for uid 1001 br@bsdpad.com; Tue, 9 Jun 2015 11:16:10 +0100 (BST) Date: Tue, 9 Jun 2015 11:16:10 +0100 From: Ruslan Bukin To: John Baldwin Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r284153 - head/sys/kern Message-ID: <20150609101610.GA47083@bsdpad.com> References: <201506081406.t58E6mvA033492@svn.freebsd.org> <20150608144629.GA37834@bsdpad.com> <1554833.IUNnl2bGYK@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1554833.IUNnl2bGYK@ralph.baldwin.cx> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2015 10:23:35 -0000 On Mon, Jun 08, 2015 at 02:04:45PM -0400, John Baldwin wrote: > On Monday, June 08, 2015 03:46:29 PM Ruslan Bukin wrote: > > For some reason it hangs for me after 'random' lines on arm64 > > Are you using dtrace? It looks like sdt was using the public symbol before > but in a context where the caller held the lock. I will revert this for now. > I think I can perhaps make it 'automatic' by having it acquire a read lock > (possibly recursing) if it doesn't already hold a write lock. > Yes, I'm using DTrace. And you right: if I remove dtrace_sdt from kernel, then the same revision works fine for me. Ruslan