-
Notifications
You must be signed in to change notification settings - Fork 5.5k
http: mitigate delayed close timeout race with connection write buffer flush #6437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 4 commits
07b5ded
82dc62d
3f08a6d
eb58ad6
b06bb0b
dd6d9ea
412f485
f60db05
11008bd
aebc8cf
0424594
efad9c6
788e07a
2d75b29
031f520
06ec3e9
e9c0a73
adb0488
012bd0a
a68c785
77ec586
0e2248c
2d3d44b
577729e
7a6bceb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -99,6 +99,7 @@ void ConnectionImpl::close(ConnectionCloseType type) { | |
|
|
||
| uint64_t data_to_write = write_buffer_->length(); | ||
| ENVOY_CONN_LOG(debug, "closing data_to_write={} type={}", *this, data_to_write, enumToInt(type)); | ||
| const bool delayed_close_timeout_set = delayedCloseTimeout().count() > 0; | ||
| if (data_to_write == 0 || type == ConnectionCloseType::NoFlush || | ||
| !transport_socket_->canFlushClose()) { | ||
| if (data_to_write > 0) { | ||
|
|
@@ -107,7 +108,13 @@ void ConnectionImpl::close(ConnectionCloseType type) { | |
| transport_socket_->doWrite(*write_buffer_, true); | ||
| } | ||
|
|
||
| closeSocket(ConnectionEvent::LocalClose); | ||
| if (type == ConnectionCloseType::FlushWriteAndDelay && delayed_close_timeout_set) { | ||
| // The socket is being closed and there is no more data to write. Since a delayed close has | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. After one more pass, is this comment correct? Arguably we can also get here where there is data to write, but we're in the midst of a tls/alts handshake and have determined that flushing is pointless (canFlushClose is false) because the write could not flush all data. I think the canFlushClose() was added for the case where you have plaintext payload queued up behind an unfinished crypto handshake at which point the payload isn't going to get flushed and given old style options you should give up and close immediately. That said, if there were some crypto protocol where there were large bidi frames, I can imagine the same race we have for HTTP where the FIN + RST lagged behind a large client side "no I am rejecting your handshake" write which is queued in the kernel and so we want a one interval delay for the client to get that response. I think if we're in that case, the connection is going to observe the transport socket is "blocked", and the alarm will fire after one interval (handling any race) so the code is doing the right thing and the comment can just be tweaked a bit for clarity. Sound right?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch, thanks for pointing this out. I have clarified the comment.
Yeah, I agree with this. I revisited the logic for the transport sockets that return |
||
| // been requested, start the delayed close timer. | ||
| initializeDelayedCloseTimer(); | ||
| } else { | ||
| closeSocket(ConnectionEvent::LocalClose); | ||
| } | ||
| } else { | ||
| ASSERT(type == ConnectionCloseType::FlushWrite || | ||
| type == ConnectionCloseType::FlushWriteAndDelay); | ||
|
|
@@ -123,35 +130,21 @@ void ConnectionImpl::close(ConnectionCloseType type) { | |
| // ConnectionManagerImpl::checkForDeferredClose() | ||
| // 2) A second close is issued by a subsequent call to | ||
| // ConnectionManagerImpl::checkForDeferredClose() prior to returning from onData() | ||
| if (delayed_close_) { | ||
| if (inDelayedClose()) { | ||
| return; | ||
| } | ||
|
|
||
| delayed_close_ = true; | ||
| const bool delayed_close_timeout_set = delayedCloseTimeout().count() > 0; | ||
|
|
||
| // NOTE: the delayed close timeout (if set) affects both FlushWrite and FlushWriteAndDelay | ||
| // closes: | ||
| // 1. For FlushWrite, the timeout sets an upper bound on how long to wait for the flush to | ||
| // complete before the connection is locally closed. | ||
| // 2. For FlushWriteAndDelay, the timeout specifies an upper bound on how long to wait for the | ||
| // flush to complete and the peer to close the connection before it is locally closed. | ||
|
|
||
| // All close types that follow do not actually close() the socket immediately so that buffered | ||
| // data can be written. However, we do want to stop reading to apply TCP backpressure. | ||
| read_enabled_ = false; | ||
|
|
||
| // Force a closeSocket() after the write buffer is flushed if the close_type calls for it or if | ||
| // no delayed close timeout is set. | ||
| close_after_flush_ = !delayed_close_timeout_set || type == ConnectionCloseType::FlushWrite; | ||
|
|
||
| // Create and activate a timer which will immediately close the connection if triggered. | ||
| // A config value of 0 disables the timeout. | ||
| if (delayed_close_timeout_set) { | ||
| delayed_close_timer_ = dispatcher_.createTimer([this]() -> void { onDelayedCloseTimeout(); }); | ||
| ENVOY_CONN_LOG(debug, "setting delayed close timer with timeout {} ms", *this, | ||
| delayedCloseTimeout().count()); | ||
| delayed_close_timer_->enableTimer(delayedCloseTimeout()); | ||
| if (!delayed_close_timeout_set || type == ConnectionCloseType::FlushWrite) { | ||
| // Force a closeSocket() after the write buffer is flushed if the close_type calls for it or | ||
| // if no delayed close timeout is set. | ||
| delayed_close_state_ = DelayedCloseState::CloseAfterFlush; | ||
| } else { | ||
| // A delayed close timer will be scheduled when the flush is completed. | ||
| delayed_close_state_ = DelayedCloseState::CloseAfterFlushAndTimeout; | ||
| } | ||
|
|
||
| file_event_->setEnabled(Event::FileReadyType::Write | | ||
|
|
@@ -162,7 +155,7 @@ void ConnectionImpl::close(ConnectionCloseType type) { | |
| Connection::State ConnectionImpl::state() const { | ||
| if (!ioHandle().isOpen()) { | ||
| return State::Closed; | ||
| } else if (delayed_close_) { | ||
| } else if (inDelayedClose()) { | ||
| return State::Closing; | ||
| } else { | ||
| return State::Open; | ||
|
|
@@ -539,9 +532,14 @@ void ConnectionImpl::onWriteReady() { | |
| // write callback. This can happen if we manage to complete the SSL handshake in the write | ||
| // callback, raise a connected event, and close the connection. | ||
| closeSocket(ConnectionEvent::RemoteClose); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need to disable timer upon closeSocket() if timer has been set or in onDelayedCloseTimeout() check if io_handle is still open? Probably I missed something in the workflow as the old code didn't do so either. But it worth commenting out why we don't do that.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I just saw that closeSocket() disables timer. Sorry for my ignorant... |
||
| } else if ((close_after_flush_ && new_buffer_size == 0) || bothSidesHalfClosed()) { | ||
| } else if ((inDelayedClose() && new_buffer_size == 0) || bothSidesHalfClosed()) { | ||
| ENVOY_CONN_LOG(debug, "write flush complete", *this); | ||
| closeSocket(ConnectionEvent::LocalClose); | ||
| if (delayed_close_state_ == DelayedCloseState::CloseAfterFlushAndTimeout) { | ||
| initializeDelayedCloseTimer(); | ||
| } else { | ||
| ASSERT(bothSidesHalfClosed() || delayed_close_state_ == DelayedCloseState::CloseAfterFlush); | ||
| closeSocket(ConnectionEvent::LocalClose); | ||
| } | ||
| } else if (result.action_ == PostIoAction::KeepOpen && result.bytes_processed_ > 0) { | ||
| for (BytesSentCb& cb : bytes_sent_callbacks_) { | ||
| cb(result.bytes_processed_); | ||
|
|
@@ -587,13 +585,22 @@ bool ConnectionImpl::bothSidesHalfClosed() { | |
| } | ||
|
|
||
| void ConnectionImpl::onDelayedCloseTimeout() { | ||
| delayed_close_timer_.reset(nullptr); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we just usually reset()
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. |
||
| ENVOY_CONN_LOG(debug, "triggered delayed close", *this); | ||
| if (connection_stats_ != nullptr && connection_stats_->delayed_close_timeouts_ != nullptr) { | ||
| connection_stats_->delayed_close_timeouts_->inc(); | ||
| } | ||
| closeSocket(ConnectionEvent::LocalClose); | ||
| } | ||
|
|
||
| void ConnectionImpl::initializeDelayedCloseTimer() { | ||
| const auto timeout = delayedCloseTimeout().count(); | ||
| ASSERT(timeout > 0); | ||
| delayed_close_timer_ = dispatcher_.createTimer([this]() -> void { onDelayedCloseTimeout(); }); | ||
| ENVOY_CONN_LOG(debug, "setting delayed close timer with timeout {} ms", *this, timeout); | ||
| delayed_close_timer_->enableTimer(delayedCloseTimeout()); | ||
| } | ||
|
|
||
| absl::string_view ConnectionImpl::transportFailureReason() const { | ||
| return transport_socket_->failureReason(); | ||
| } | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -167,16 +167,22 @@ class ConnectionImpl : public virtual Connection, | |
| // Callback issued when a delayed close timeout triggers. | ||
| void onDelayedCloseTimeout(); | ||
|
|
||
| void initializeDelayedCloseTimer(); | ||
| bool inDelayedClose() const { return delayed_close_state_ != DelayedCloseState::None; } | ||
|
|
||
| static std::atomic<uint64_t> next_global_id_; | ||
|
|
||
| // States associated with delayed closing of the connection (i.e., when the underlying socket is | ||
| // not immediately close()d as a result of a ConnectionImpl::close()). | ||
| enum class DelayedCloseState { None, CloseAfterFlush, CloseAfterFlushAndTimeout }; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you add comments for each state? It's not immediately clear what the difference is between the latter 2.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done. |
||
| DelayedCloseState delayed_close_state_{DelayedCloseState::None}; | ||
|
|
||
| Event::Dispatcher& dispatcher_; | ||
| const uint64_t id_; | ||
| Event::TimerPtr delayed_close_timer_; | ||
| std::list<ConnectionCallbacks*> callbacks_; | ||
| std::list<BytesSentCb> bytes_sent_callbacks_; | ||
| bool read_enabled_{true}; | ||
| bool close_after_flush_{false}; | ||
| bool delayed_close_{false}; | ||
| bool above_high_watermark_{false}; | ||
| bool detect_early_close_{true}; | ||
| bool enable_half_close_{false}; | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe update here as well? It can still trigger, but won't trigger if progress is being made?