-
Notifications
You must be signed in to change notification settings - Fork 531
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
Ftp::Gateway may segfault in level-3 double-complete debugs() #1923
Ftp::Gateway may segfault in level-3 double-complete debugs() #1923
Conversation
Ftp::Gateway::completeForwarding() must check that both Control and Data connections are still available before dereferencing them.
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.
Thank you for fixing this bug! I have adjusted PR title and description to highlight that this bug is specific to level-3 debugging, may not be triggered in every double-complete case, and that the ugly solution mimics existing Ftp::Relay::abortOnData() code. Please adjust further as needed.
Long-term, we should do better, but this minimal fix is enough for now.
@yadij, |
Ftp::Gateway::completeForwarding() must check data.conn pointer before dereferencing it. Long-term, we should improve Comm::ConnectionPointer printing to safely report Connection::id (where available). This minimal fix just mimics existing Ftp::Relay::abortOnData() solution.
Ftp::Gateway::completeForwarding() must check data.conn pointer before
dereferencing it. Long-term, we should improve Comm::ConnectionPointer
printing to safely report Connection::id (where available). This minimal
fix just mimics existing Ftp::Relay::abortOnData() solution.