Date: Mon, 26 Jun 2006 17:48:20 -0600 From: Brad Waite <freebsd@wcubed.net> To: Max Laier <max@love2party.net> Cc: freebsd-stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: 6.1-stable hangs and LORs Message-ID: <44A07244.4090409@wcubed.net> In-Reply-To: <200606120024.59336.max@love2party.net> References: <448C5C41.10302@wcubed.net> <20060611213635.GA35430@xor.obsecurity.org> <448C8F3B.5020806@wcubed.net> <200606120024.59336.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey Max, thanks big-time for the help! It's been just over 2 weeks with no LORs and no lockups. I've read the man page probably a hundred times when setting up pf, but never saw the bug. Wanted to confirm the fix with anyone else that may be struggling like I was. Would it be out of the question to throw a notice to syslog() if the user or group filter? That would have saved me months of frustration. Brad Max Laier wrote: > From pf.conf(5): > 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. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44A07244.4090409>