diff options
| author |   tb <tb@openbsd.org> | 2021-01-02 18:00:08 +0000 |
|---|---|---|
| committer | tb <tb@openbsd.org> | 2021-01-02 18:00:08 +0000 |
| commit | 0b1548030915b7a3f3689f668dcfb1481dbdcd11 (patch) | |
| tree | c4b1c900b7ac33325827d3aeec6dd79e36226c13 /gnu/llvm/libcxx/benchmarks/algorithms.partition_point.bench.cpp | |
| parent | Remove libunwind 8.0.0 now that we switched to libunwind 11.0.0 in the (diff) | |
| download | wireguard-openbsd-0b1548030915b7a3f3689f668dcfb1481dbdcd11.tar.xz wireguard-openbsd-0b1548030915b7a3f3689f668dcfb1481dbdcd11.zip | |
Free {alert,phh}_data in tls13_record_layer_free()
httpd(8)'s incorrect tls_close() after closing the underlying socket
led to a leak: tls_close()'s attempt to send out the close_notify won't
work very well over a closed pipe. This resulted in alert_data still
hanging off the TLSv1.3 context's record layer struct. The tls_free()
call should have cleaned this up but failed to do so.
The record layer's phh_data potentially has the same issue, so free it
as well. This diff makes -current httpd(8) run in constant memory over
hundreds of thousands TLS connections with a static site.
ok inoguchi jsing
Diffstat (limited to 'gnu/llvm/libcxx/benchmarks/algorithms.partition_point.bench.cpp')
0 files changed, 0 insertions, 0 deletions