glebius d989f8363f It may happen that pfsync holds the last reference on a state. In this ...

case keys had already been freed. If encountering such state, then
just release last reference.

Not sure this can happen as a runtime race, but can be reproduced by
the following scenario:

- enable pfsync
- disable pfsync
- wait some time
- enable pfsync

2012-11-07 07:30:40 +00:00

..

if_pflog.c

Make the "struct if_clone" opaque to users of the cloning API. Users

2012-10-16 13:37:54 +00:00

if_pfsync.c

It may happen that pfsync holds the last reference on a state. In this

2012-11-07 07:30:40 +00:00

in4_cksum.c

…

pf_if.c

…

pf_ioctl.c

Revert previous commit...

2012-10-10 08:36:38 +00:00

pf_lb.c

Make ruleset anchors in pf(4) reentrant. We've got two problems here:

2012-09-18 10:54:56 +00:00

pf_norm.c

…

pf_osfp.c

…

pf_ruleset.c

…

pf_table.c

When connection rate hits and we overload a source to a table,

2012-09-22 10:14:47 +00:00

pf.c

o Remove last argument to ip_fragment(), and obtain all needed information

2012-10-26 21:06:33 +00:00