On Sun, Mar 02, 2008 at 03:58:50PM +0100, Luigi Rizzo wrote:
The SI_ORDER_* definitions in /sys/sys/kernel.h are enumerated on a
large range, so if the existing code does not have races,
you can safely move the non-leaf modules
(such as ipfw,ko in your case) to (SI_ORDER_ANY -
Current FreeBSD problem reports
Critical problems
Serious problems
S Tracker Resp. Description
o kern/51274 ipfw [ipfw] [patch] ipfw2 create dynamic rules with parent
o kern/73910 ipfw
Hi Paolo Pisati!
On Sun, 2 Mar 2008 16:13:10 +0100; Paolo Pisati wrote about 'Re: ipfw
initialization: SI_ORDER_ANY - SI_ORDER_MIDDLE?':
i just found out that depending on a KLD doesn't imply any
initialization order, thus depending on a lock initialized in the ipfw
init path is _really_ a
On Mon, Mar 03, 2008 at 11:17:19AM +0100, Paolo Pisati wrote:
On Sun, Mar 02, 2008 at 03:58:50PM +0100, Luigi Rizzo wrote:
The SI_ORDER_* definitions in /sys/sys/kernel.h are enumerated on a
large range, so if the existing code does not have races,
you can safely move the non-leaf
