Date: Wed, 2 Apr 2003 17:35:23 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Nate Lawson <nate@root.org> Cc: current@freebsd.org Subject: Re: mbuf LOR Message-ID: <16011.26027.758879.203450@grasshopper.cs.duke.edu> In-Reply-To: <Pine.BSF.4.21.0304021235150.12236-100000@root.org> References: <Pine.BSF.4.21.0304021235150.12236-100000@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16011.26027.758879.203450>