You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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: