Date: Wed, 25 Aug 2004 00:05:10 +1000 From: Tim Robbins <tjr@freebsd.org> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: panic: getnewbuf: locked buf Message-ID: <20040824140510.GA26058@cat.robbins.dropbear.id.au> In-Reply-To: <20040824133420.GI77326@green.homeunix.org> References: <20040824142129.S96700@cvs.imp.ch> <20040824124516.GA25734@cat.robbins.dropbear.id.au> <20040824144832.S96700@cvs.imp.ch> <20040824125818.GA25828@cat.robbins.dropbear.id.au> <20040824133420.GI77326@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 24, 2004 at 09:34:20AM -0400, Brian Fundakowski Feldman wrote: > On Tue, Aug 24, 2004 at 10:58:18PM +1000, Tim Robbins wrote: > > On Tue, Aug 24, 2004 at 02:48:57PM +0200, Martin Blapp wrote: > > > > > > Hi, > > > > > > > This has already been fixed in -CURRENT and will presumably be merged into > > > > RELENG_5 in the next day or two. > > > > > > Can you point me to the responsable commit ? > > > > kern_lock.c 1.75 > > Releasing 5.3 with lockmgr(9) known-broken in one way versus the other > really is no better. I suppose it would have been more accurate to say that it had been worked around, not fixed, in -CURRENT. This is definitely something that needs to be properly addressed before the release. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040824140510.GA26058>