From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 14:32:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BBBC16A4CE; Thu, 8 Jan 2004 14:32:36 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25AE443D6B; Thu, 8 Jan 2004 14:32:18 -0800 (PST) (envelope-from bz@zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 93B701FF91D; Thu, 8 Jan 2004 23:32:16 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 0525A1FF90C; Thu, 8 Jan 2004 23:32:14 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 54CD8154EC; Thu, 8 Jan 2004 22:32:05 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 4A020153CA; Thu, 8 Jan 2004 22:32:06 +0000 (UTC) Date: Thu, 8 Jan 2004 22:32:06 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: "Bjoern A. Zeeb" In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de X-Mailman-Approved-At: Thu, 08 Jan 2004 16:38:22 -0800 cc: sam@freebsd.org cc: core@kame.net cc: current@freebsd.org cc: "Bjoern A. Zeeb" cc: ume@freebsd.org Subject: Re: [PATCH] IPSec fixes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 22:32:36 -0000 On Thu, 8 Jan 2004, Bjoern A. Zeeb wrote: Hi, > Can someone please review and test them. I will do this too this evening > but as 5.2 is about to be build I guess and I have seen more reports > about IPSec related panics I thought any additional 12 hours might be > good [even if they will not be included in 5.2R]. thanks to all who have replied and had/have a look at it. I am now running a 5.2-CURRENT #0: Thu Jan 8 21:02:11 UTC 2004 including but not actually using INET6 with only the submitted ipsec related patches and nothing else related to this problem domain in my patchset. Is up, running fine, have not been able to crash it. Tried all possible ways I had success with before w/o the patches. Hopefully someone can give a positive response on the review so I can delete those 55M of console logs from debugging ;-) -- Greetings and g'night Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/ tech support excuse #418: Repeated reboots of the system failed to solve problem