From owner-freebsd-net@FreeBSD.ORG Sat Feb 11 06:39:08 2006 Return-Path: X-Original-To: net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2A5D16A420 for ; Sat, 11 Feb 2006 06:39:08 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 582B643D48 for ; Sat, 11 Feb 2006 06:39:08 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (unknown [2001:200:0:8002:644a:1300:9f15:d623]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 8D33F1521E; Sat, 11 Feb 2006 15:39:06 +0900 (JST) Date: Sat, 11 Feb 2006 15:38:56 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Kris Kennaway In-Reply-To: <20060211035025.GA77114@xor.obsecurity.org> References: <20060116004438.GA27901@xor.obsecurity.org> <20060207054502.GA18560@xor.obsecurity.org> <20060211035025.GA77114@xor.obsecurity.org> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: net@FreeBSD.org Subject: Re: Changing time causes ipv6 panics 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: Sat, 11 Feb 2006 06:39:08 -0000 >>>>> On Fri, 10 Feb 2006 22:50:25 -0500, >>>>> Kris Kennaway said: >> Sorry, not really (we've not got a test environment to reproduce it). >> But from a quick review of nd6.c, there seems to be one thing that is >> obviously wrong. The possible bug has been there since rev. 1.19 >> committed in April 2002. We've been probably just lucky so far... >> >> Could you try the patch attached below? We'll probably also need to >> apply this fix to 4.X and 5.X. > The patch did not fix the panic. Hmm, but this time the point where the panic happened should be different. Can you identify where it was? >> (a note about the patch: the first chunk is actually not related to >> the bug, but I could not miss the trivial typo) > You missed the other one though :-) That's right:-) I was informed of that one off-list. >> - * However, from a stricter speci-confrmance standpoint, we should >> + * However, from a stricter spec-confrmance standpoint, we should > ^o JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp