From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 22:38:12 2004 Return-Path: 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 9DFC916A4CF for ; Thu, 19 Aug 2004 22:38:12 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5FC143D31 for ; Thu, 19 Aug 2004 22:38:11 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i7JMZ5Vt067902 for freebsd-current@freebsd.org.checked; (8.12.8/vak/2.1) Fri, 20 Aug 2004 02:35:05 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by hanoi.cronyx.ru with ESMTP id i7JMXtCb067859 for ; (8.12.8/vak/2.1) Fri, 20 Aug 2004 02:33:55 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <41252924.4020305@cronyx.ru> Date: Fri, 20 Aug 2004 02:26:44 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.2.1) Gecko/20030426 X-Accept-Language: ru-ru, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Tracking down LORs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Aug 2004 22:38:12 -0000 Hi, Currently I am trying to track down a couple of LORS in my code. But it seems that I do not undestand smth or all things id realy so bad. So I want to ask some questions to find out if my thoughts correct or wrong. 1. If I am right LOR means that we have at least two mutexs. Lets call them a and b. If we set a, then b in first case and b then a in second we could get dead loop, and thus LOR. 2. If I have some driver that have mutex a, and we have some sytem code that could call this driver with Giant (b), we would get LOR if driver lock a and some other part of system will try to lock Giant? or I am wrong? rik