Skip to content
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

Kill established session threads when we kill SMB server #18754

Open
bwatters-r7 opened this issue Jan 26, 2024 · 0 comments
Open

Kill established session threads when we kill SMB server #18754

bwatters-r7 opened this issue Jan 26, 2024 · 0 comments
Assignees
Labels
suggestion-feature New feature suggestions

Comments

@bwatters-r7
Copy link
Contributor

While testing #18680, I saw that if you kill all the services, the thread listening on port 445 goes away, but the threads serving the established connections do not. If I establish an SMB session, then kill all the smb servers, nothing is listening on 445, but I can still download and interact with the share on an established connection, even though it says no services are there.
This makes sense if we are rigidly defining the service as the listener, which I could see, but it means that the servicing threads will continue to run well after the service is gone; we just won't accept new connections.

See #18680 (comment)

@bwatters-r7 bwatters-r7 added the suggestion-feature New feature suggestions label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion-feature New feature suggestions
Projects
None yet
Development

No branches or pull requests

2 participants