Date: Fri, 12 Dec 2003 16:46:29 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: jroberson@chesapeake.net Cc: freebsd-current@FreeBSD.org Subject: Re: vn_fullpath: 0xc85e24a0 is not locked but should be Message-ID: <200312130046.hBD0kTeF059375@gw.catspoiler.org> In-Reply-To: <20031212184001.C4201-100000@mail.chesapeake.net>
index | next in thread | previous in thread | raw e-mail
On 12 Dec, Jeff Roberson wrote: > On Fri, 12 Dec 2003, Don Lewis wrote: >> DEBUG_VFS_LOCKS is quite usable as long as you don't run find, tar, etc. >> that traverses procfs. > > This isn't entirely relevant, but I'd like to point out how happy I am > that it works even this much. When I started fixing up VFS we couldn't > even run init without DEBUG_VFS_LOCKS panicing. It took me a few weeks of > hacking to get the system running anything useful with all of these > assertions. A lot of other people have put significant effort in along > the way as well. I'm very happy to see the progress. Both of my -CURRENT machines run with DEBUG_VFS_LOCKS enabled. It is very rare that I run into problems. Doing funny things with procfs is one way to trigger assertion failures, and I think there might be a bug or two left in nullfs and/or unionfs, but I don't use those. It's probably wise to write down the proper DDB incantations to disable the code triggered by the assertion failures in case you get into trouble.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312130046.hBD0kTeF059375>