Hi Kristof,
yes we use pfsync. Yesterday we tried with pfsync switched off, the box
still locked up but this time without a panic.
We make the DIOCRADDADDRS ioctl on the master and the backup (we use
CARPed pairs).
Regards Joe Jones
On 01/03/18 03:00, Kristof Provost wrote:
On 28 Feb 2018, at 9:52, Kristof Provost wrote:
On 27 Feb 2018, at 20:40, Joe Jones wrote:
we have a kernel panic after compiling with witness and invariant
Feb 27 13:49:33 sovapn1 kernel: lock order reversal:
Feb 27 13:49:33 sovapn1 kernel: 1st 0xfffffe000fed78b8 pf_idhash
(pf_idhash) @ /usr/src/sys/netpfil/pf/pf.c:1078
Feb 27 13:49:33 sovapn1 kernel: 2nd 0xfffff8001e0474a8 pfsync
(pfsync) @ /usr/src/sys/netpfil/pf/if_pfsync.c:1667
That’s a lock order reversal. It’s not good, but it should at worst
result in a deadlock. Did the system stop after this?
It also looks like a different problem from the panic you initially
reported.
Also, do you actively use pfsync in this setup? Does the panic happen
on the box where you DIOCRADDADDRS or the other(s)?
Regards,
Kristof
_______________________________________________
freebsd-pf@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-pf
To unsubscribe, send any mail to "freebsd-pf-unsubscr...@freebsd.org"
