Page MenuHomeFreeBSD

pfsync: Correctly check if bpf peers are present
ClosedPublic

Authored by zlei on Jun 7 2024, 6:04 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 31, 3:23 PM
Unknown Object (File)
Oct 8 2024, 11:43 AM
Unknown Object (File)
Oct 5 2024, 10:38 AM
Unknown Object (File)
Oct 5 2024, 10:15 AM
Unknown Object (File)
Oct 5 2024, 1:57 AM
Unknown Object (File)
Oct 3 2024, 3:28 PM
Unknown Object (File)
Oct 3 2024, 3:26 PM
Unknown Object (File)
Oct 3 2024, 1:27 PM

Details

Summary

On creating the pfsync(4) interface, pfsync_clone_create() does an
unconditional bpfattach(). Use bpf_peers_present() which was introduced
in commit 16d878cc99ef [1] to check the presence of bpf peers.

This will save a little CPU cycles and memory usage when the synchronisation interface
is not configured and there is no bpf peers present. There should be no functional change.

  1. 16d878cc99ef Fix the following bpf(4) race condition which can result in a panic

MFC after: 1 week

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable