Page MenuHomeFreeBSD

ktls: Write-lock the INP when changing a transmit TLS session.
ClosedPublic

Authored by jhb on Jan 28 2022, 9:30 PM.
Tags
None
Referenced Files
F132112243: D34086.id102686.diff
Mon, Oct 13, 8:01 PM
F132112242: D34086.id102185.diff
Mon, Oct 13, 8:01 PM
F132112240: D34086.id102061.diff
Mon, Oct 13, 8:01 PM
F132112239: D34086.id.diff
Mon, Oct 13, 8:01 PM
Unknown Object (File)
Mon, Oct 13, 6:32 AM
Unknown Object (File)
Thu, Oct 9, 11:28 PM
Unknown Object (File)
Wed, Oct 1, 9:06 PM
Unknown Object (File)
Sep 12 2025, 5:55 PM

Details

Summary

The TCP rate pacing code relies on being able to read this pointer
safely while holding an INP lock. The initial TLS session pointer is
set while holding the write lock already.

Diff Detail

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

Event Timeline

jhb requested review of this revision.Jan 28 2022, 9:30 PM
This revision is now accepted and ready to land.Jan 28 2022, 9:49 PM

Is it allowed to lock the INP after SOCKBUF? I thought you needed to lock INP first, then SOCKBUF?

  • Lock INP before socket buffer.
This revision now requires review to proceed.Feb 1 2022, 12:42 AM
This revision is now accepted and ready to land.Feb 1 2022, 9:57 AM