From owner-freebsd-current@FreeBSD.ORG Sun Oct 17 08:45:10 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 EA31C16A4DC; Sun, 17 Oct 2004 08:45:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B93D43D2D; Sun, 17 Oct 2004 08:45:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 7196E1FF9AC; Sun, 17 Oct 2004 10:45:08 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id A177C1FF9AB; Sun, 17 Oct 2004 10:45:06 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 5EBCE15606; Sun, 17 Oct 2004 08:44:52 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 53B43154FC; Sun, 17 Oct 2004 08:44:53 +0000 (UTC) Date: Sun, 17 Oct 2004 08:44:53 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: gnn@freebsd.org 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 cc: FreeBSD current mailing list Subject: Re: 6-CUR: panic in ipsec processing w/o ipsec in use 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: Sun, 17 Oct 2004 08:45:11 -0000 On Sun, 17 Oct 2004 gnn@freebsd.org wrote: Hi, > At Sat, 16 Oct 2004 19:39:00 +0000 (UTC), > Bjoern A. Zeeb wrote: > > > > Hi, > > > > on my MP machine running 6-CURRENT from around late 2004-09-26 > > I got a panic while editing a Makefile of a port; though compiled in > > I have no ipsec in use on that machine atm. > > > > hand transcribed: > > panic > > free +0xaa > > _key_delsp +0x1b > > key_delsp +0xab > > _key_freesp +0x8a > > ipsec4_hdrsiz +0x9b > > ipsec4_hdrsiz_tc +0xa9 > > tcp_output +0x9c1 > > tcp_usr_send +0x18b > > sosend +0x5e7 > > soo_write +0x46 > > dofilewrite +0xa8 > > write +0x39 > > syscall > > Xint0x80_syscall > > > > > > the bt looks strange to me, so I decided to post though > > this may already be corrected ? > > This might be related to a fix, that needs testing, with respect to > the mbuf data size. The thing I'm thinking about is this: > > There are reports that racoon is unable to complete IKE negotiation > due to a send to the pfkey socket returning ENOBUFS. This appears to > be a result of an incorrect assumption about mbuf data size due to a > change resulting from mbuma. A fix for this is in RELENG_5 now. I know but as said: "no ipsec in use on that machine". The questions are: a) why does anything go into the ipsec processing path if I do not use ipsec (no policies, no SAs, no raccon, ...)? b) why does this happen from dofilewrite? > You might want to update your system. yeah I might want to do that. > From what you say in your email this looks like an intermittent > error. Have you been able to reproduce this? no. it just happened this one time in ~14 days. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT