From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 14:35:32 2003 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 2A89737B404 for ; Wed, 2 Apr 2003 14:35:32 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 690D143FA3 for ; Wed, 2 Apr 2003 14:35:31 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h32MZSMS008702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Apr 2003 17:35:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h32MZNp31130; Wed, 2 Apr 2003 17:35:23 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16011.26027.758879.203450@grasshopper.cs.duke.edu> Date: Wed, 2 Apr 2003 17:35:23 -0500 (EST) To: Nate Lawson In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@freebsd.org Subject: Re: mbuf LOR 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: Wed, 02 Apr 2003 22:35:32 -0000 Nate Lawson writes: > I was testing some changes to make fxp MPSAFE and got a LOR in allocating > the mbuf cluster and then finally a panic when trying to dereference the > cluster header. Is the mbuf system MPSAFE? Is it ok to call m_getcl > with a device lock held (but not Giant)? > > The lock reversal was: 1. fxp softc lock, 2. Giant. > > Traceback: > zalloc... > malloc() > mb_pop_cont() > mb_alloc() > m_getcl() > fxp_add_rfabuf() > fxp_intr_body() > fxp_intr() -- locks fxp softc I thought that this had been fixed. Which zalloc() exactly? Drew