-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
NULL pointer dereference #15399
Comments
Second time:
|
Looks like one of the panics in #11679 to me. The bug is, to my understanding, that when native encryption was added, it started keeping an additional potential copy of the encrypted data, in addition to potentially the decrypted copy, which violates some assumptions in the code about there only being one potential thing you need to check for being owned in a specific edge case, leading to a race condition where if that assumption being violated lines up correctly with a specific series of operations that assume they're safe to do if there's only one person looking at them, and you know you're looking at it since you have a reference to it, ... |
More:
|
I expect this to be already fixed by #16104 in master. It is likely too fresh for upcoming 2.2.4, but should appear in following 2.2.5 release. |
System information
Describe the problem you're observing
NULL pointer dereference while receiving an encrypted dataset. Does not seem to be the same as any other open or closed issue.
Describe how to reproduce the problem
First time this has happened.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: