linux-kernel - Re: [PATCH RFC] fs/binfmt_elf: fix memory map for PIE applications

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 19 Dec 2013 15:17:03 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Timo Teräs <timo.teras@....fi>
cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] fs/binfmt_elf: fix memory map for PIE applications

On Wed, 2 Oct 2013, Timo Teräs wrote:

> arch/*/include/asm/elf.h comments say:
>   ELF_ET_DYN_BASE is the location that an ET_DYN program is loaded
>   if exec'ed.  Typical use of this is to invoke "./ld.so someprog"
>   to test out a new version of the loader.  We need to make sure
>   that it is out of the way of the program that it will "exec",
>   and that there is sufficient room for the brk.
> 
> In case we have main application linked as PIE, this can cause
> problems as the main program itself is being loaded to this
> alternate address. And this allows limited heap size. While
> this is inevitable when exec'ing the interpreter directly,
> we should do better for PIE applications.

Timo,

could you please provide more specific example of the breakage scenario 
you are talking about? It's not completely clear to me from your commit 
message.

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/