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.
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
Update libssh to 0.11.1 #3735
base: main
Are you sure you want to change the base?
Update libssh to 0.11.1 #3735
Changes from all commits
25c3b38
8298caf
0e2e120
1da0449
bc304c7
895c11d
74267c2
8e76021
e186630
2cc9974
055d2fe
c5d9200
c9f2ff6
92c8746
a3e240e
4d1c44a
3e8b0e7
ada20ce
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 81 in src/platform/console/unix_console.cpp
Codecov / codecov/patch
src/platform/console/unix_console.cpp#L81
Check warning on line 165 in src/platform/platform_unix.cpp
Codecov / codecov/patch
src/platform/platform_unix.cpp#L165
Check warning on line 167 in src/platform/platform_unix.cpp
Codecov / codecov/patch
src/platform/platform_unix.cpp#L167
Check warning on line 170 in src/platform/platform_unix.cpp
Codecov / codecov/patch
src/platform/platform_unix.cpp#L170
Check warning on line 172 in src/platform/platform_unix.cpp
Codecov / codecov/patch
src/platform/platform_unix.cpp#L172
Check warning on line 175 in src/platform/platform_unix.cpp
Codecov / codecov/patch
src/platform/platform_unix.cpp#L175
Check warning on line 177 in src/platform/platform_unix.cpp
Codecov / codecov/patch
src/platform/platform_unix.cpp#L177
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.
About this change, I think the
timeout_secs
is used to set theSSH_OPTIONS_TIMEOUT
, and this option is the timeout value for ssh session connection establishment wait time (not entire sure about this, hard to find a clear documentation as well). Therefore, having a reasonable value (like the original 20 seconds) seems to makes sense here.Besides, with your watchdog fix ( which is essentially checking the sftp_threading running together with other SIGQUIT, SIGTERM, SIGHUP signals), the program already behaves correctly. So I am doubting whether we still make the time out change here. What do you think?
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.
Wasn't this a keep-alive timeout? A better var name might help here.
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.
The program will not behave correctly with a reasonable timeout unfortunately. After the timeout expires, the sshfs_server process will exit, the watchdog fix makes it so that it doesn't hang. It behaves like a keep-alive timeout, but libssh has no keep-alive messages.
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.
ok, so it looks like a keep-alive timeout as opposed to ssh session connection establishment wait time, interesting. It is a weird option offered to users though.
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.
I do have a wondering here though, the
SSH_OPTIONS_TIMEOUT
is the a ssh option. If it were a keep-alive timeout, should it be the timeout of ssh session alive? If so, should themultipass shell
hang without mount?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.
multipass shell
doesn't hang since it's setup to automatically reconnect. You can see this behavior in #3810 where the SSH session is restarting every 20 seconds. Also with normal use it's much more likely there is some SSH traffic within the 20 seconds compared to SFTP which is likely to not get any traffic for long periods of time.Check warning on line 187 in src/sshfs_mount/sshfs_mount.cpp
Codecov / codecov/patch
src/sshfs_mount/sshfs_mount.cpp#L187
Check warning on line 189 in src/sshfs_mount/sshfs_mount.cpp
Codecov / codecov/patch
src/sshfs_mount/sshfs_mount.cpp#L189