From owner-freebsd-current@FreeBSD.ORG Sun May 27 15:53:06 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8C2916A4C8; Sun, 27 May 2007 15:53:06 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.freebsd.org (Postfix) with ESMTP id 5DD3913C46C; Sun, 27 May 2007 15:53:06 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.14.1/8.14.1/NinthNine) with SMTP id l4RFr4AL048621; Mon, 28 May 2007 00:53:04 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Mon, 28 May 2007 00:53:03 +0900 From: Norikatsu Shigemura To: Andre Oppermann Message-Id: <20070528005303.575c114d.nork@FreeBSD.org> In-Reply-To: <4654CBDE.5000902@freebsd.org> References: <20070520223104.d8c53e57.nork@FreeBSD.org> <4654CBDE.5000902@freebsd.org> X-Mailer: Sylpheed 2.4.0 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Mon, 28 May 2007 00:53:05 +0900 (JST) Cc: Norikatsu Shigemura , current@FreeBSD.org Subject: Re: panic: tcp_log_addrs: string too long X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 27 May 2007 15:53:06 -0000 On Thu, 24 May 2007 01:18:54 +0200 Andre Oppermann wrote: > Norikatsu Shigemura wrote: > > Hi andre! > > I have a tcp_log_addrs panic issue like following (with my patch). > > I didn't know why 'string too long'. So I added following patch > > to report this issue. Do you have any idea? > It is fixed in netinet/tcp_subr.c rev. 1.285. Please update your system. I confirmed that this issue was fixed! Thank you!