Re: patch: VFS: fix passing of AT_PHDR value in auxv to ELF interpreter

Quentin Godfroy wrote:
> +	elf_ppnt = elf_phdata;
> +	for (i = 0; i< loc->elf_ex.e_phnum; i++, elf_ppnt++)
> +		if (elf_ppnt->p_type == PT_PHDR) {
> +			phdr_addr = elf_ppnt->p_vaddr;
>   

Won't this break with ET_DYN executables?  And besides, isn't this the
same thing?  Shouldn't PT_PHDR->p_vaddr point to the vaddr of the Phdr
table itself?

    J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: patch: VFS: fix passing of AT_PHDR value in auxv to ELF interpreter
    • From: Quentin Godfroy <[email protected]>

• References:
  • patch: VFS: fix passing of AT_PHDR value in auxv to ELF interpreter
    • From: Quentin Godfroy <[email protected]>

• Prev by Date: Re: [PATCH] Blacklist Dell Optiplex 320 from using the HPET
• Next by Date: Re: cpufreq longhaul locks up
• Previous by thread: Re: patch: VFS: fix passing of AT_PHDR value in auxv to ELF interpreter
• Next by thread: Re: patch: VFS: fix passing of AT_PHDR value in auxv to ELF interpreter
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]