mendersoftware / mender / 2264857152

80%

master: 81%

push

gitlab-ci

fix: use boost beast's tcp_stream object

Scheduled async read handlers from boost beast takes a stream
object which we close and destroy in error handlers. The issue is that on
cases where we call the error handler with our custom timeout, we
destroy the stream object which some async read operations still need
access to. By leveraging boost beast's own tcp_stream object, we can get rid
of our custom timeout and set the timeout directly in the object which
will allow the async error handler to do its job.

Ticket: MEN-9104
Changelog: Fixed use-after-free errors when freeing tcp stream socket
which pending async read handlers needed access to.

Signed-off-by: Daniel Skinstad Drabitzius <daniel.drabitzius@northern.tech>

11 of 14 new or added lines in 1 file covered. (78.57%)

7874 of 9887 relevant lines covered (79.64%)

13908.65 hits per line