-
Notifications
You must be signed in to change notification settings - Fork 30k
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
zlib: Fix use after null when calling .close #5982
zlib: Fix use after null when calling .close #5982
Conversation
An internal zlib error may cause _handle to be set to null. Close now will check if there is a _handle prior to calling .close on it.
LGTM |
LGTM too, if that’s worth anything. Adding a test for this should not be too complicated, I think? |
I will give a shot adding a test tonight thanks for quick r? |
LGTM. +1 to a test. |
LGTM with a test |
ping @lightsofapollo ... have you had a chance to look at the test yet? |
CI: https://ci.nodejs.org/job/node-test-commit/2962/ |
needs to be included with f8e507e when backported |
An internal zlib error may cause _handle to be set to null. Close now will check if there is a _handle prior to calling .close on it. PR-URL: nodejs#5982 Fixes: nodejs#6034 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Pull Request check-list
Please make sure to review and check all of these items:
make -j8 test
(UNIX) orvcbuild test nosign
(Windows) pass withthis change (including linting)?
test (or a benchmark) included?
existing APIs, or introduces new ones)?
NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Affected core subsystem(s)
Description of change
An internal zlib error may cause _handle to be set to null.
Close now will check if there is a _handle prior to calling .close on
it.