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?
to your account
Submitted by: @AlexPeshkoff
Due to different bytes order in lck_long member of union in class Lock, upper bytes (always zero for LCK_page_space locks) are taken into an account on bigendians. This breaks normal operation of page spaces.
Commits: 7456868 6e6ab6b 17a218f be9afc2
The text was updated successfully, but these errors were encountered:
assignee: Alexander Peshkov [ alexpeshkoff ]
Sorry, something went wrong.
Commented by: @AlexPeshkoff
Makes no sense using 2-bytes long lock values - 4-bytes use same memory (it's anyway allocated aligned) and work with same speed (also due to alignment in shared memory).
Therefore lck_length is set to sizeof(long) for this type of lock.
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 2.5 RC1 [ 10362 ]
Fix Version: 2.1.4 [ 10361 ]
status: Resolved [ 5 ] => Closed [ 6 ]
QA Status: No test
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: No test => Cannot be tested
Successfully merging a pull request may close this issue.