summaryrefslogtreecommitdiffstats
path: root/sys/modules/pflog
diff options
context:
space:
mode:
authorcsjp <csjp@FreeBSD.org>2006-09-12 04:25:13 +0000
committercsjp <csjp@FreeBSD.org>2006-09-12 04:25:13 +0000
commit63e89c05d2dd3463fdb87ade28334a74d7c6e6f0 (patch)
treebfad0bcbfb5566e8fc5f5992840f671a03dba9ea /sys/modules/pflog
parentc74e70f7a8f39a60078eafdfacb3a154e190b0f8 (diff)
downloadFreeBSD-src-63e89c05d2dd3463fdb87ade28334a74d7c6e6f0.zip
FreeBSD-src-63e89c05d2dd3463fdb87ade28334a74d7c6e6f0.tar.gz
Introduce a new entry point, mac_create_mbuf_from_firewall. This entry point
exists to allow the mandatory access control policy to properly initialize mbufs generated by the firewall. An example where this might happen is keep alive packets, or ICMP error packets in response to other packets. This takes care of kernel panics associated with un-initialize mbuf labels when the firewall generates packets. [1] I modified this patch from it's original version, the initial patch introduced a number of entry points which were programmatically equivalent. So I introduced only one. Instead, we should leverage mac_create_mbuf_netlayer() which is used for similar situations, an example being icmp_error() This will minimize the impact associated with the MFC Submitted by: mlaier [1] MFC after: 1 week This is a RELENG_6 candidate
Diffstat (limited to 'sys/modules/pflog')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud