Currently on ARM64 with 4K pages set, GDB fails to load the VDSO with
the error "Failed to read a valid object file image from memory" as it
is applying the phdr alignment to the vma, and attempting to read below
where the VDSO is mapped. This is because our segment alignment is 64K
in the ELF headers, but the VDSO only has PAGE_SIZE alignment from
get_unmapped_area.
Work around this by calling vm_unmapped_area directly, and specifying
the worst case alignment (64K) directly.
With this patch applied, I no longer have issues loading the VDSO in
gdb (and no more error message every time I run a program inside it.)
Signed-off-by: Kyle McMartin <redacted>
@@ -163,7 +163,18 @@ int arch_setup_additional_pages(struct linux_binprm *bprm,vdso_mapping_len=(vdso_pages+1)<<PAGE_SHIFT;down_write(&mm->mmap_sem);-vdso_base=get_unmapped_area(NULL,0,vdso_mapping_len,0,0);+{+/* the VDSO must be worst-case aligned to 64K */+structvm_unmapped_area_infoinfo=+{+.flags=0,+.length=vdso_mapping_len,+.low_limit=mm->mmap_base,+.high_limit=TASK_SIZE,+.align_mask=(1<<16)-1,+};+vdso_base=vm_unmapped_area(&info);+}if(IS_ERR_VALUE(vdso_base)){ret=vdso_base;gotoup_fail;
From: Will Deacon <hidden> Date: 2014-01-16 17:44:19
Hi Kyle,
On Wed, Jan 15, 2014 at 09:41:44PM +0000, Kyle McMartin wrote:
quoted hunk
Currently on ARM64 with 4K pages set, GDB fails to load the VDSO with
the error "Failed to read a valid object file image from memory" as it
is applying the phdr alignment to the vma, and attempting to read below
where the VDSO is mapped. This is because our segment alignment is 64K
in the ELF headers, but the VDSO only has PAGE_SIZE alignment from
get_unmapped_area.
Work around this by calling vm_unmapped_area directly, and specifying
the worst case alignment (64K) directly.
With this patch applied, I no longer have issues loading the VDSO in
gdb (and no more error message every time I run a program inside it.)
Signed-off-by: Kyle McMartin <redacted>
@@ -163,7 +163,18 @@ int arch_setup_additional_pages(struct linux_binprm *bprm,vdso_mapping_len=(vdso_pages+1)<<PAGE_SHIFT;down_write(&mm->mmap_sem);-vdso_base=get_unmapped_area(NULL,0,vdso_mapping_len,0,0);+{+/* the VDSO must be worst-case aligned to 64K */+structvm_unmapped_area_infoinfo=+{+.flags=0,+.length=vdso_mapping_len,+.low_limit=mm->mmap_base,+.high_limit=TASK_SIZE,+.align_mask=(1<<16)-1,+};+vdso_base=vm_unmapped_area(&info);+}
I don't like this fix. The kernel is perfectly alright mapping the vdso at
the actual page size, as opposed to the maximum. Since the vdso isn't
demand-paged, we can actually just tell the linker not to bother forcing 64k
(worst case) alignment for PT_LOAD segments. Please can you try the patch
below?
Will
--->8
I don't like this fix. The kernel is perfectly alright mapping the vdso at
the actual page size, as opposed to the maximum. Since the vdso isn't
demand-paged, we can actually just tell the linker not to bother forcing 64k
(worst case) alignment for PT_LOAD segments. Please can you try the patch
below?
Me either, tbh. ;-)
I was testing out using -Wl,-z,max-page-size for the
!CONFIG_ARM64_64K_PAGES case, and that seemed to work. A quick compile
check shows the segment alignment being 0x10 with -Wl,-n:
kmcmarti ~/linux $ eu-readelf -l
arch/arm64/kernel/vdso/vdso.so
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz
MemSiz Flg Align
LOAD 0x000000 0x0000000000000000 0x0000000000000000 0x000700
0x000700 R E 0x10
so I think that should work nicely!
I'll reboot a machine with this fix to test it as soon as possible.
Acked-by: Kyle McMartin <redacted>