Date: Mon, 20 Aug 2007 12:43:25 -0400 From: "Scott Ullrich" <sullrich@gmail.com> To: "VANHULLEBUS Yvan" <vanhu_bsd@zeninc.net> Cc: freebsd-net@freebsd.org Subject: Re: Racoon(ipsec-tools) enters sbwait state or 100% CPU utilization quite often on RELENG_1_2 Message-ID: <d5992baf0708200943h708f4a21xd111a5264a7f4f65@mail.gmail.com> In-Reply-To: <20070820082728.GA28863@zen.inc> References: <d5992baf0708171353j7e7563a8y8dca4475779bc410@mail.gmail.com> <20070818102803.GA1319@jayce.zen.inc> <d5992baf0708181258t501e5842y6b8bdee8a5c2e07c@mail.gmail.com> <m27ins2pby.wl%gnn@neville-neil.com> <20070820082728.GA28863@zen.inc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/20/07, VANHULLEBUS Yvan <vanhu_bsd@zeninc.net> wrote: > 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..... Thank you Yvan and George! The PR has been filed and the ID# is kern/115651 I have added some interesting notes that seem to affect NetBSD as well. We will be happy to work with anyone to get this solved and access to the machine in question is available if need be. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d5992baf0708200943h708f4a21xd111a5264a7f4f65>