rodrigc added a comment. I can confirm that:
kldunload -f pf.ko does work to unload the module. That is good. I saw this warning message in dmesg: lock order reversal: (sleepable after non-sleepable) 1st 0xffffffff823b72e0 pf rulesets (pf rulesets) @ /opt2/branches/head/sys/modules/pf/../../netpfil/pf/pf_ioctl.c:321 2nd 0xffffffff818f99a0 umadrain (umadrain) @ /opt2/branches/head/sys/vm/uma_core.c:2109 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe04639fd310 witness_checkorder() at witness_checkorder+0xe26/frame 0xfffffe04639fd3a0 _sx_slock() at _sx_slock+0x76/frame 0xfffffe04639fd3e0 uma_zdestroy() at uma_zdestroy+0x23/frame 0xfffffe04639fd400 pf_normalize_cleanup() at pf_normalize_cleanup+0x26/frame 0xfffffe04639fd420 pf_vnet_uninit() at pf_vnet_uninit+0x6e7/frame 0xfffffe04639fd8c0 vnet_deregister_sysuninit() at vnet_deregister_sysuninit+0x9c/frame 0xfffffe04639fd900 linker_file_unload() at linker_file_unload+0x45e/frame 0xfffffe04639fd950 kern_kldunload() at kern_kldunload+0x12f/frame 0xfffffe04639fd9a0 amd64_syscall() at amd64_syscall+0x27f/frame 0xfffffe04639fdab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe04639fdab0 If possible, it would be good to clean that up. REVISION DETAIL https://reviews.freebsd.org/D1944 EMAIL PREFERENCES https://reviews.freebsd.org/settings/panel/emailpreferences/ To: nvass-gmx.com, bz, zec, trociny, glebius, rodrigc, kristof, gnn Cc: julian, robak, freebsd-virtualization, freebsd-pf, freebsd-net _______________________________________________ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
