-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
NPE in testsuite logged when using Conscrypt. #7988
Comments
@ejona86 @carl-mastrangelo @nmittler who would be the best to ping on your end ? |
Yep, that's probably just a bug in Conscrypt. Can you tell me what you're doing to trigger that? |
When calling wrap() on a closed SSLEngine instance, we check to see if anything is already pending to be written, but the native BIO will already have been freed, so the native code threw NullPointerException. Check for it being already freed when looking for pending data and just return zero in thta case. Also sets the bio pointer to 0 before freeing it and and marks it as volatile to reduce the chances of any weird race conditions, though the locking in ConscryptEngine should already make these impossible. Fixes netty/netty#7988.
Nevermind, I see through the stack trace that this is due to calling |
Thanks... left a comment there
… Am 31.05.2018 um 12:30 schrieb Adam Vartanian ***@***.***>:
Nevermind, I see through the stack trace that this is due to calling wrap() on a closed SSLEngine. That obviously shouldn't throw NPE. I've uploaded a fix for review.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
When calling wrap() on a closed SSLEngine instance, we check to see if anything is already pending to be written, but the native BIO will already have been freed, so the native code threw NullPointerException. Check for it being already freed when looking for pending data and just return zero in that case. Also sets the bio pointer to 0 before freeing it and and marks it as volatile to reduce the chances of any weird race conditions, though the locking in ConscryptEngine should already make these impossible. Fixes netty/netty#7988.
Okay, this should be fixed at head. I expect to make our next release on Monday. |
Thanks... would be nice if you could just comment here once done
… Am 31.05.2018 um 21:06 schrieb Adam Vartanian ***@***.***>:
Okay, this should be fixed at head. I expect to make our next release on Monday.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
…sing conscrypt. Motivation: When using conscrypt some NPEs were logged, these were fixed in the latest release. Modifications: Update to conscrypt 1.1.3. Result: Fixes #7988.
…ng conscrypt. Motivation: When using conscrypt some NPEs were logged, these were fixed in the latest release. Modifications: Update to conscrypt 1.1.3. Result: Fixes #7988.
Saw this during the build:
Most interesting is this:
I wonder if this is just a bug in conscrypt ?
The text was updated successfully, but these errors were encountered: