From owner-freebsd-current@FreeBSD.ORG Wed Jul 1 21:42:47 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 372B11065691; Wed, 1 Jul 2009 21:42:47 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0B9348FC21; Wed, 1 Jul 2009 21:42:47 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 7D88D46B8E; Wed, 1 Jul 2009 17:42:46 -0400 (EDT) Date: Wed, 1 Jul 2009 22:42:46 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jung-uk Kim In-Reply-To: <200907011737.15525.jkim@FreeBSD.org> Message-ID: References: <20090701162108.GA33681@regency.nsu.ru> <200907011613.10550.jkim@FreeBSD.org> <200907011737.15525.jkim@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Alexey Dokuchaev , freebsd-current@FreeBSD.org Subject: Re: Kernel panic with if_sf.ko 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: Wed, 01 Jul 2009 21:42:48 -0000 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