From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17668 invoked by alias); 1 Dec 2006 09:50:18 -0000 Received: (qmail 17655 invoked by uid 22791); 1 Dec 2006 09:50:15 -0000 X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,BAYES_50,NO_REAL_NAME,SPF_PASS X-Spam-Check-By: sourceware.org Received: from snape.ecoscentric.com (HELO snape.ecoscentric.com) (212.13.207.199) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 01 Dec 2006 09:50:10 +0000 Received: by snape.ecoscentric.com (Postfix, from userid 48) id CACDC2C00B; Fri, 1 Dec 2006 09:50:07 +0000 (GMT) From: bugzilla-daemon@ecoscentric.com To: ecos-bugs@sources.redhat.com Subject: [Bug 1000347] New: FreeBSD Network Thread misses incoming packet enque in ether_demux X-Bugzilla-Reason: QAcontact Message-Id: <20061201095007.CACDC2C00B@snape.ecoscentric.com> Date: Sat, 09 Dec 2006 21:09:00 -0000 Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-bugs-owner@sourceware.org X-SW-Source: 2006/txt/msg00561.txt.bz2 http://bugzilla.ecoscentric.com/show_bug.cgi?id=1000347 Summary: FreeBSD Network Thread misses incoming packet enque in ether_demux Product: eCos Version: unknown Platform: All OS/Version: All Status: UNCONFIRMED Severity: normal Priority: high Component: TCPIP AssignedTo: gary@mlbassoc.com ReportedBy: bugzilla_rmvthis@ds3switch.com QAContact: ecos-bugs@sources.redhat.com If the priority of the ethernet driver thread is lower (higher #) than the FreeBSD Network Thread, then the Network Thread can get prematurely woken up to process an incoming ethernet pkt before the packet is fully enqued. Specifically: if_ethersubr:ether_demux() calls schednetisr() (which wakes up network thread) prior to the pkt being enqued with that call to IF_ENQUEUE(). This might not be obvious because a subsequent incoming packet can (partially) process the queue. -- Configure bugmail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.