Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.
From: Ilya Smith <hidden>
Date: 2018-03-30 09:07:58
Also in:
linux-mips, linux-mm, linux-s390, linux-sh, linuxppc-dev, lkml, sparclinux
Possibly related (same subject, not in this thread)
- 2018-04-03 · Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap. · Ilya Smith <hidden>
- 2018-03-28 · Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap. · Ilya Smith <hidden>
- 2018-03-28 · RE: [RFC PATCH v2 0/2] Randomization of address chosen by mmap. · "Luck, Tony" <tony.luck@intel.com>
- 2018-03-28 · Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap. · Ilya Smith <hidden>
- 2018-03-28 · Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap. · Ilya Smith <hidden>
Hi
On 30 Mar 2018, at 10:55, Pavel Machek [off-list ref] wrote: Hi!quoted
Current implementation doesn't randomize address returned by mmap. All the entropy ends with choosing mmap_base_addr at the process creation. After that mmap build very predictable layout of address space. It allows to bypass ASLR in many cases. This patch make randomization of address on any mmap call.How will this interact with people debugging their application, and getting different behaviours based on memory layout? strace, strace again, get different results?
Honestly I’m confused about your question. If the only one way for debugging application is to use predictable mmap behaviour, then something went wrong in this live and we should stop using computers at all. Thanks, Ilya