From owner-freebsd-net@FreeBSD.ORG Fri Mar 7 23:20:02 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7333B1065671 for ; Fri, 7 Mar 2008 23:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 62B0A8FC13 for ; Fri, 7 Mar 2008 23:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m27NK2jR058156 for ; Fri, 7 Mar 2008 23:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m27NK2uL058131; Fri, 7 Mar 2008 23:20:02 GMT (envelope-from gnats) Date: Fri, 7 Mar 2008 23:20:02 GMT Message-Id: <200803072320.m27NK2uL058131@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Bruce Cran Cc: Subject: Re: kern/92552: A serious bug in most network drivers from 5.X to 6.X (regression) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Cran List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 23:20:02 -0000 The following reply was made to PR kern/92552; it has been noted by GNATS. From: Bruce Cran To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/92552: A serious bug in most network drivers from 5.X to 6.X (regression) Date: Fri, 07 Mar 2008 23:18:23 +0000 Hi, Sorry it's taken such a long time to get around to looking at this problem report. I'm not very familiar with the network code but from looking at if_em.c it appears that a dual locking implementation was added in rev 1.65.2.28 (FreeBSD 6.3) so that the core lock is held by both the ioctl and interrupt handlers and so this problems should no longer occur. However, the _CORE_LOCK macros are only used in if_em so unless the problem has been fixed in the other network drivers this problem will still exist. Do you remember which other network drivers are affected? Thanks, Bruce