Date: Tue, 2 Mar 1999 17:28:13 -0600 From: Alan Cox <alc@cs.rice.edu> To: Brian Feldman <green@unixhelp.org> Cc: current@freebsd.org Subject: Re: lockmgr panic with mmap() Message-ID: <19990302172813.A91146@nonpc.cs.rice.edu> In-Reply-To: <Pine.BSF.4.05.9903021816130.9317-100000@janus.syracuse.net>; from Brian Feldman on Tue, Mar 02, 1999 at 06:16:50PM -0500 References: <19990302113704.B90473@nonpc.cs.rice.edu> <Pine.BSF.4.05.9903021816130.9317-100000@janus.syracuse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 02, 1999 at 06:16:50PM -0500, Brian Feldman wrote: > > Where exactly does thrd_sleep come in, since that's where the program locks > up now? Can't be killed, of course... > The lock manager isn't bright enough to detect that the process already holds a read lock when it attempts to get the write lock. Thus, you get the "thrd_sleep" instead of a panic. In short, same bug, different symptoms. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990302172813.A91146>