Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Jan 2008 19:35:05 -0600
From:      "Bill Marquette" <bill.marquette@gmail.com>
To:        "Max Laier" <max@love2party.net>
Cc:        "freebsd-pf@freebsd.org" <freebsd-pf@freebsd.org>
Subject:   Re: LOR in pf on 6.2
Message-ID:  <55e8a96c0801291735g4a356d17p2871b6673e446cb5@mail.gmail.com>
In-Reply-To: <32841.192.168.4.151.1201635351.squirrel@router.laiers.local>
References:  <55e8a96c0801291037r7bd013cfr6f3c6448024afd42@mail.gmail.com> <32841.192.168.4.151.1201635351.squirrel@router.laiers.local>

next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 29, 2008 1:35 PM, Max Laier <max@love2party.net> wrote:
> From the pf.conf(5) in RELENG_6_2:
>
> BUGS
>   Due to a lock order reversal (LOR) with the socket layer, the use of the
>   group and user filter parameter in conjuction with a Giant-free netstack
>   can result in a deadlock.  If you have to use group or user you must set
>   debug.mpsafenet to ``0'' from the loader(8), for the moment.  This work-
>   around will still produce the LOR, but Giant will protect from the dead-
>   lock.

Crud, didn't see that...I was suspecting the user/group code.  Thanks
Max, I'll pull that from our ruleset immediately.

--Bill



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55e8a96c0801291735g4a356d17p2871b6673e446cb5>