From owner-freebsd-net@FreeBSD.ORG Mon Aug 20 08:27:32 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F20F16A419 for ; Mon, 20 Aug 2007 08:27:32 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 3024913C428 for ; Mon, 20 Aug 2007 08:27:31 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id B87703F1F; Mon, 20 Aug 2007 10:27:28 +0200 (CEST) Date: Mon, 20 Aug 2007 10:27:28 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070820082728.GA28863@zen.inc> References: <20070818102803.GA1319@jayce.zen.inc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: All mail clients suck. This one just sucks less. Cc: Scott Ullrich Subject: Re: Racoon(ipsec-tools) enters sbwait state or 100% CPU utilization quite often on RELENG_1_2 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 08:27:32 -0000 On Sun, Aug 19, 2007 at 12:08:49PM +0900, George V. Neville-Neil wrote: [....] > Please file a PR and assign it to me. > > I read your kernel config, and it seems you were using FAST_IPSEC, and > not Kame IPsec, so I'm wondering how relevant Yvan's comment might > be. I think we should look a bit more deeply at this. I tracked down the problem a few years ago, on FreeBSD 4.11, with KAME's IPSec stack. But the problem was not really in the stack itself, but rather in socket processing (in other words: not in netkey/*, but in kern/uipc_socket2.c). And as both IPSec stacks shares some PFKey constraints (for example one message per entry when dumping SADB / SPD), I guess the same problem existed in FAST_IPSEC. But when I had some time a few months ago to start filling a PR for the problem, I had a look at FreeBSD6 source code, and I noticed that sbspace macro (which was a quite important part of the problem) has changed, and I didn't have the required setup to do the test again, so I just can't be really sure the problem still exists... But the reported problem really has similar symptoms..... Yvan. -- NETASQ http://www.netasq.com