Page MenuHomeFreeBSD

Enter and exit the network epoch for async IPsec callbacks.
ClosedPublic

Authored by jhb on Jun 25 2020, 12:49 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Oct 11, 10:52 AM
Unknown Object (File)
Fri, Oct 10, 3:00 AM
Unknown Object (File)
Mon, Oct 6, 9:30 PM
Unknown Object (File)
Sep 14 2025, 6:04 AM
Unknown Object (File)
Sep 13 2025, 9:31 PM
Unknown Object (File)
Sep 12 2025, 10:06 PM
Unknown Object (File)
Sep 9 2025, 3:48 PM
Unknown Object (File)
Aug 16 2025, 5:21 AM
Subscribers

Details

Summary

When an IPsec packet has been encrypted or decrypted, the next step in
the packet's traversal through the network stack is invoked from a
crypto worker thread, not from the original calling thread. These
threads need to enter the network epoch before passing packets down to
IP output routines or up to transport protocols.

Test Plan
  • tried IPsec with a kernel with INVARIANTS on head and it promptly fell over with assertion failures (not sure why I didn't see this previously since the assertions went in)
  • tested with IPv4 (AES-GCM, IPcomp (sort of, I was able to get a single ping reply back, but not others), AES-CBC + SHA1), and IPv6 (AES-GCM)

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable