From owner-freebsd-stable@FreeBSD.ORG Sat Sep 8 07:59:55 2007 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EB4D16A418 for ; Sat, 8 Sep 2007 07:59:55 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.freebsd.org (Postfix) with ESMTP id CD5FA13C442 for ; Sat, 8 Sep 2007 07:59:54 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.0.68] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id l887xmYa028135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 8 Sep 2007 00:59:53 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <46E25620.6050906@FreeBSD.org> Date: Sat, 08 Sep 2007 00:58:24 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Kostik Belousov References: <46E19D4E.1060009@FreeBSD.org> <20070908040233.GP53667@deviant.kiev.zoral.com.ua> In-Reply-To: <20070908040233.GP53667@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org Subject: Re: kqueue LOR X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Sep 2007 07:59:55 -0000 Kostik Belousov wrote: > On Fri, Sep 07, 2007 at 11:49:50AM -0700, Maxim Sobolev wrote: >> Hi, >> >> On my 6.2 system I am seeing LOR discussed almost 1 year ago here: >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/031048.html >> http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031197.html >> >> lock order reversal: >> 1st 0xc52cb500 kqueue (kqueue) @ kern/kern_event.c:1547 >> 2nd 0xc4e4d80c struct mount mtx (struct mount mtx) @ >> ufs/ufs/ufs_vnops.c:138 >> >> Do you have any plans to commit the suggested fix? > I suspect that the LOR is bogus. I was never able to get the information > where the reverse lock order happen. What I asked of the most reporters is > to apply sys/kern/subr_witness.c rev. 1.222 to RELENG_6 and provide me > with the LOR report, if any. What do you mean "bogus"? It happens reliably on my system. > Note that doing that on RELENG_6_2 makes no sense, most likely you will > get LORs with cdev mutex, fixed in RELENG_6. I don't quite understand that. -Maxim