>>> On 01.03.16 at 12:59, wrote:
> Changes since v4:
> - Add a define that contains the number of sections.
> - Improve the comment to describe the memory layout.
> - Check that the sh_link field is 0 < sh_link < e_shnum.
> - Simplify some of the logic, since the SYMTAB section is already
>
>>> On 01.03.16 at 19:25, wrote:
> Roger Pau Monne writes ("[PATCH v5] libelf: rewrite symtab/strtab loading"):
>> Current implementation of elf_load_bsdsyms is broken when loading inside of
>> a HVM guest, because it assumes elf_memcpy_safe is able to write into guest
>> memory space, which it is
Roger Pau Monne writes ("[PATCH v5] libelf: rewrite symtab/strtab loading"):
> Current implementation of elf_load_bsdsyms is broken when loading inside of
> a HVM guest, because it assumes elf_memcpy_safe is able to write into guest
> memory space, which it is not.
>
> Take the oportunity to do so
On Tue, Mar 01, 2016 at 12:59:50PM +0100, Roger Pau Monne wrote:
> Current implementation of elf_load_bsdsyms is broken when loading inside of
> a HVM guest, because it assumes elf_memcpy_safe is able to write into guest
> memory space, which it is not.
>
> Take the oportunity to do some cleanup a
Current implementation of elf_load_bsdsyms is broken when loading inside of
a HVM guest, because it assumes elf_memcpy_safe is able to write into guest
memory space, which it is not.
Take the oportunity to do some cleanup and properly document how
elf_{parse/load}_bsdsyms works. The new implementa
