Re: kern/46118: pppoe(4) via axe(4) triggers locking-related panic

[David Holland <dholland-gnats%netbsd.org@localhost>]

The following reply was made to PR kern/46118; it has been noted by GNATS.

From: David Holland <dholland-gnats%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/46118: pppoe(4) via axe(4) triggers locking-related panic
Date: Sun, 2 Jun 2013 00:45:02 +0000

 not sent to gnats
 
    ------
 
 From: Michael van Elst <mlelstv%serpens.de@localhost>
 To: gnats%netbsd.org@localhost
 Subject: Re: kern/46118: pppoe(4) via axe(4) triggers locking-related panic
 Date: Tue, 26 Mar 2013 13:56:01 +0100
 
 
 Locking is supposed to occur on a higher layer. Most calls into
 an if_start routine come through ifq_enqueue() which protects
 the if_start routine by aquiring the kernel lock.
 
 Some code however does not use ifq_enqueue() but calls if_start
 directly, and none if it cares about the kernel lock. In particular:
 
 - ppp / pppoe
 - sl
 - strip
 - ieee1394
 - bridge
 - vlan
 
 netipsec and net80211 might have similar problem paths.
 
 
 Greetings,
 -- 
                                 Michael van Elst
 Internet: mlelstv%serpens.de@localhost
                                 "A potential Snark may lurk in every tree."