Date: Wed, 10 Aug 2005 08:31:09 +0200 From: Thierry Herbelot <thierry@herbelot.com> To: freebsd-current@freebsd.org Cc: kan@freebsd.org, Don Lewis <truckman@freebsd.org> Subject: Re: panic: lock (sleep mutex) vnode interlock not locked Message-ID: <200508100831.11384.thierry@herbelot.com> In-Reply-To: <200508100611.j7A6B6qf099212@gw.catspoiler.org> References: <200508100611.j7A6B6qf099212@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Wednesday 10 August 2005 08:11, Don Lewis a écrit : > > I also noticed this inconsistency in vgonel() a couple hours ago and > made exactly the same change in my local source. No problems so far, > but I suspect this bug is difficult to trigger. It's been present in As I wrote before, I saw it twice yesterday - it was in the initial "rm -r" phase of "make buildworld" > the code for a couple of months. maybe a code change "elsewhere" made it more probable (the LOCK/UNLOCK infrastructure everywhere in the kernel code begins to be scary : difficult to follow, difficult to prove right ?) TfH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508100831.11384.thierry>