Date: Sat, 11 Feb 2006 15:38:56 +0900 From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp> To: Kris Kennaway <kris@obsecurity.org> Cc: net@FreeBSD.org Subject: Re: Changing time causes ipv6 panics Message-ID: <y7vwtg2flhb.wl%jinmei@isl.rdc.toshiba.co.jp> In-Reply-To: <20060211035025.GA77114@xor.obsecurity.org> References: <20060116004438.GA27901@xor.obsecurity.org> <20060207054502.GA18560@xor.obsecurity.org> <y7vhd7bjwye.wl%jinmei@isl.rdc.toshiba.co.jp> <20060211035025.GA77114@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Fri, 10 Feb 2006 22:50:25 -0500, >>>>> Kris Kennaway <kris@obsecurity.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y7vwtg2flhb.wl%jinmei>