Index: pf.conf.5 =================================================================== RCS file: /usr/store/mlaier/fcvs/src/contrib/pf/man/pf.conf.5,v retrieving revision 1.2 diff -u -r1.2 pf.conf.5 --- pf.conf.5 14 Sep 2004 01:07:19 -0000 1.2 +++ pf.conf.5 3 Oct 2004 10:24:17 -0000 @@ -28,7 +28,7 @@ .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" -.Dd September 14, 2004 +.Dd October 03, 2004 .Dt PF.CONF 5 .Os .Sh NAME @@ -1316,6 +1316,17 @@ Similar to .Ar user , this rule only applies to packets of sockets owned by the specified group. +.Pp +The use of +.Ar group +or +.Ar user +in +.Va debug.mpsafenet Ns = Ns 1 +environments may result in a deadlock. +Please see the +.Sx BUGS +section for details. .It Ar user This rule only applies to packets of sockets owned by the specified user. For outgoing connections initiated from the firewall, this is the user @@ -2610,6 +2621,23 @@ .It Pa /usr/share/examples/pf Example rulesets. .El +.Sh BUGS +Due to a lock order reversal (LOR) with the socket layer, the use of the +.Ar group +and +.Ar user +filter parameter in conjuction with a Giant-free netstack +can result in a deadlock. If you have to use +.Ar group +or +.Ar user +you must set +.Va debug.mpsafenet +to "0" from the +.Xr loader 8 , +for the moment. +This workaround will still produce the LOR, but Giant will protect from the +deadlock. .Sh SEE ALSO .Xr icmp 4 , .Xr icmp6 4 ,