From owner-cvs-src@FreeBSD.ORG Sat Jan 12 01:30:19 2008 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3BEA16A41A; Sat, 12 Jan 2008 01:30:19 +0000 (UTC) (envelope-from mux@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id DED2B13C4EE; Sat, 12 Jan 2008 01:30:19 +0000 (UTC) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id DCFCD1A4D7E; Fri, 11 Jan 2008 17:10:35 -0800 (PST) Date: Sat, 12 Jan 2008 02:10:35 +0100 From: Maxime Henrion To: Mike Tancsa Message-ID: <20080112011035.GA5752@elvis.mu.org> References: <200801091538.m09Fcn0w050430@repoman.freebsd.org> <200801091554.m09FsnUC049542@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200801091554.m09FsnUC049542@lava.sentex.ca> User-Agent: Mutt/1.4.2.3i Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/net route.c route.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2008 01:30:20 -0000 Mike Tancsa wrote: > At 10:38 AM 1/9/2008, Maxime Henrion wrote: > >mux 2008-01-09 15:38:49 UTC > > > > FreeBSD src repository > > > > Modified files: (Branch: RELENG_6) > > sys/net route.c route.h > > Log: > > MFC route.c@1.125 and route.h@1.68: > > Add a workaround for a deadlock between the rt_setgate() and rt_check() > > functions. It is easily triggered by running routed, and, I expect, by > > running any other daemon that uses routing sockets. > > Hi, > I have a number of boxes running full bgp tables with > Quagga. How does the deadlock manifest itself ? I havent seen the > boxes lockup ? Or does the deadlock create other symptoms ? > > ---Mike > It resulted in a hard lockup for us, but it's possible there are other different outcomes in different scenarios. For details on the specific deadlock I have observed, see thread 'Deadlock in the routing code' on freebsd-net@. Cheers, Maxime