Date: Wed, 1 Jul 2009 22:42:46 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: Alexey Dokuchaev <danfe@nsu.ru>, freebsd-current@FreeBSD.org Subject: Re: Kernel panic with if_sf.ko Message-ID: <alpine.BSF.2.00.0907012241550.27367@fledge.watson.org> In-Reply-To: <200907011737.15525.jkim@FreeBSD.org> References: <20090701162108.GA33681@regency.nsu.ru> <200907011613.10550.jkim@FreeBSD.org> <alpine.BSF.2.00.0907012116370.27367@fledge.watson.org> <200907011737.15525.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Jul 2009, Jung-uk Kim wrote: >>> Last time I checked, bpf(4) with MAC caused a similar problem when it is >>> destroying bpf descriptor label. GENERIC includes MAC by default now. >>> If you don't need MAC, try removing "options MAC" from your kernel >>> configuration. >> >> I was not aware of this problem -- could you provide some more details? >> Any panic caused by having MAC in the kernel is a bug... > > It was about a month ago. I had funny impression that you and sam were > working on it cause it started happening when sam added bpf detach event > handler and MAC was enabled by default. Any way, I will let you know if I > can reproduce the problem. There have been a number of tear-down related races for ifnets, more of which are closed now than before the last few weeks, but none MAC-related as far as I'm aware. If it recurs, please let me know and I'm happy to help investigate (MAC-related or otherwise). Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0907012241550.27367>