Date: Wed, 1 Sep 2004 02:52:11 +0900 (JST) From: Norikatsu Shigemura <nork@FreeBSD.org> To: rwatson@FreeBSD.org Cc: nork@FreeBSD.org Subject: Re: ping6 -f panic with mpsafenet=1 Message-ID: <200408311752.i7VHqB6B009470@sakura.ninth-nine.com> In-Reply-To: <200408311744.i7VHiEWl009249@sakura.ninth-nine.com> References: <200408301502.i7UF2L7f030909@sakura.ninth-nine.com> <Pine.NEB.3.96L.1040830224045.30366C-100000@fledge.watson.org> <200408311744.i7VHiEWl009249@sakura.ninth-nine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Sep 2004 02:44:14 +0900 (JST) Norikatsu Shigemura <nork@FreeBSD.org> wrote: > > > > I contacted a panic on current with debug.mpsafenet=1. > > > > - - - - - - - - - - > > > > # ping6 -f othermachine > > > (snip) > > > INET6 with FAST_IPSEC will contact panic. But INET6 with > > > KAME_IPSEC is safe, because forced disable mpsafenet on boot. > > Do you get a panic with INET6 and FAST_IPSEC yet with mpsafenet disabled? > Yes, I confirmed that INET6 and FAST_IPSEC with debug.mpsafenet=0 ~~~ Oops "No" > doesn't causes panic. Pointed out by: hrs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408311752.i7VHqB6B009470>