Re: fixes for ipfw and pf lock ordering issues

From: Max Laier (max_at_love2party.net)
Date: 09/25/04

  • Next message: Bruce M Simpson: "Re: execute a user process in the kernel" 
    To: "Christian S.J. Peron" <csjp@freebsd.org>
Date: Sat, 25 Sep 2004 00:55:55 +0200

    On Saturday 25 September 2004 00:37, Christian S.J. Peron wrote:
    > Good day folks, we need some beta testers
    >
    > Currently, those who utilize ucred based firewalling, i.e. firewall
    > rules which match based on UID, GID or JAIL ID are subject to lock order
    > problems which often results in the system hard locking. (when giant
    > is not present ... debug.mpsafenet=1).
    >
    > This problem affects all FreeBSD firewalls which implement ucred based
    > matching, namely ipfw and pf. The lock order problem exists due to a
    > layering violation which occurs when the IP stack attempts to acquire
    > locks within lower level stacks such as UDP and TCP.

    For the record [just realized that we forgot]: Talking about LOR id 14-17 ... 

    -- 
/"\  Best regards,                      | mlaier@freebsd.org
\ /  Max Laier                          | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | mlaier@EFnet
/ \  ASCII Ribbon Campaign              | Against HTML Mail and News

  • Next message: Bruce M Simpson: "Re: execute a user process in the kernel"