lib: revert addition of vtysh_flush() call in vty_out() (backport #19109) #19154
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This partially reverts commit 9112fb3. It is not permissible/possible to call vtysh_flush() from vty_out() as it may unexpectedly close the vty. This is only permitted to happen during a VTY event triggered from the event loop, not from a vty_out() call in a random place mid-code. The socket buffer size changes are left in place. Signed-off-by: David Lamparter <equinox@opensourcerouting.org> (cherry picked from commit 1c50a1e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts the
vtysh_flush()part of #16672 since it is just plain not permissible to do that. There's a cascaded partial revert of #17571, but that was only a minor adjustment and it remains intact in the general sense.A better/correct fix would be to do something like engineering a
vtysh_try_flush()function; but I'd prefer to not do that on stable versions, so here's a revert to get back to functionally correct before we take another go at the memory spike problem.cf. #19040 for related discussion (this revert should make that PR unnecessary)
This is an automatic backport of pull request #19109 done by Mergify.