-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a brute-force workaround for the issue, basically this would
convert the hard deadlock into another problem (no multicast/broadcast
being done on bridge, if CARP is enabled). It's good enough for my
usage but is of course far from ideal.
As I
On Mon, Jul 13, 2009 at 8:40 PM, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> This LOR is observed in an environment with both CARP and bridge set up.
> Is this an known one?
>
> lock order reversal:
>
> 1st 0xff00033253e0 carp_if (carp_if) @
> /usr/src/sys/neti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
This LOR is observed in an environment with both CARP and bridge set up.
Is this an known one?
lock order reversal:
1st 0xff00033253e0 carp_if (carp_if) @
/usr/src/sys/netinet/ip_carp.c:1326
2nd 0xff00031d1218 if_bridge (if_bridge) @
