Date: Tue, 16 Jun 2009 08:12:03 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: current@freebsd.org, Doug Rabson <dfr@freebsd.org>, pav@freebsd.org, Kip Macy <kmacy@freebsd.org> Subject: Re: pointyhat panic Message-ID: <200906160812.04284.jhb@freebsd.org> In-Reply-To: <20090616073353.GZ33280@droso.net> References: <1242075474.72992.118.camel@hood.oook.cz> <3c1674c90906151408n6febec56m140b089b694f6e13@mail.gmail.com> <20090616073353.GZ33280@droso.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 16 June 2009 3:33:55 am Erwin Lansing wrote: > On Mon, Jun 15, 2009 at 02:08:17PM -0700, Kip Macy wrote: > > This is from the RPC re-work. I had thought that this was fixed. You > > shouldn't see this on the latest -CURRENT, but Doug will have more > > details. > > Any datepoint when these fixes went in? I upgraded pointyhat last month > exactly to get the latest fixes in, but could be there were more since > then. You want the socket upcall locking changes in 193272 (committed June 1). You will also want subsequent commits to the RPC and NFS code by Rick Macklem to close a few more races. I think Rick still has one other patch that pho@ is stress testing as well. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906160812.04284.jhb>