ASSERT "ma->start + ma->os_data.alignment == base" #4256
Assignees
Labels
Comments
sapostolakis
added a commit
that referenced
this issue
Apr 26, 2021
Prevents triggering ASSERT_CURIOSITY for duplicated elf headers for debug DR builds on AArch64 systems with 64K pages. In such systems, it is possible for small modules (less than 1 page of disk space) to have multiple RW LOADable data segments. Since these segments are mapped from a single disk space they will all have an elf header. The previously available check assumed that there can only be one RW data segment. For AArch64 systems with 64K pages, extend this check to accommodate for more than one data segments. Fixes: #4256
sapostolakis
added a commit
that referenced
this issue
Apr 27, 2021
…ch64 (#4876) Prevents triggering an ASSERT_CURIOSITY for duplicated elf headers for debug DR builds on AArch64 systems. It is possible for small modules (less than 1 page of disk space) to have multiple LOAD data segments. Since these segments are mapped from a single disk page they will all have an elf header. The triggered assertion assumed that there can only be one data segment. Extends this assertion check to accommodate for more than one data segments. Adds a comment reporting an assumption in DR module code for a single segment alignment. Fixes: #4256
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This happens reliably in a proprietary AArch64 app running on ThunderX2 on a 5.3.12-222-64kb kernel:
I have not looked into the details; just filing various issues seen with this app and then will go back through them.
The text was updated successfully, but these errors were encountered: