aboutsummaryrefslogtreecommitdiff
path: root/malloc/alloc_buffer_alloc_array.c
diff options
context:
space:
mode:
authorSzabolcs Nagy <szabolcs.nagy@arm.com>2022-08-08 09:22:44 +0100
committerSzabolcs Nagy <szabolcs.nagy@arm.com>2022-10-27 14:46:52 +0100
commitc511eea647f5f4ccf65a817da746bb10f4bbc2cf (patch)
treeaefa3da546d1bcf02c97d91b54e6c9584b8d7ef6 /malloc/alloc_buffer_alloc_array.c
parent15458dd00f538c02becb3ec01192adf0e4a58a9d (diff)
downloadglibc-c511eea647f5f4ccf65a817da746bb10f4bbc2cf.tar.xz
glibc-c511eea647f5f4ccf65a817da746bb10f4bbc2cf.zip
cheri: elf: add an RW capability to link_map
For each module keep an RX and an RW root capability. Use the existing l_map_start for RX (covering all load segments) and add l_rw_start for RW (covering all writable load segments). For relocation processing, we also need individual RW ranges to decide which objects need to be derived from RW and RX capabilities. In practice most modules have exactly one RW segment and it's unlikely that any module needs more than four distinct ranges to tightly cover the RW mappings. Only added on CHERI targets so always has to be used behind ifdef.
Diffstat (limited to 'malloc/alloc_buffer_alloc_array.c')
0 files changed, 0 insertions, 0 deletions