[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <95EECC28-7349-4FB4-88BF-26E4CF087A0B@gmail.com>
Date: Fri, 30 Mar 2018 12:07:58 +0300
From: Ilya Smith <blackzert@...il.com>
To: Pavel Machek <pavel@....cz>
Cc: rth@...ddle.net, ink@...assic.park.msu.ru, mattst88@...il.com,
vgupta@...opsys.com, linux@...linux.org.uk, tony.luck@...el.com,
fenghua.yu@...el.com, jhogan@...nel.org, ralf@...ux-mips.org,
jejb@...isc-linux.org, Helge Deller <deller@....de>,
benh@...nel.crashing.org, paulus@...ba.org, mpe@...erman.id.au,
schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
ysato@...rs.sourceforge.jp, dalias@...c.org, davem@...emloft.net,
tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
x86@...nel.org, nyc@...omorphy.com, viro@...iv.linux.org.uk,
arnd@...db.de, gregkh@...uxfoundation.org, deepa.kernel@...il.com,
Michal Hocko <mhocko@...e.com>, hughd@...gle.com,
kstewart@...uxfoundation.org, pombredanne@...b.com,
akpm@...ux-foundation.org, steve.capper@....com,
punit.agrawal@....com, paul.burton@...s.com,
aneesh.kumar@...ux.vnet.ibm.com, npiggin@...il.com,
keescook@...omium.org, bhsharma@...hat.com, riel@...hat.com,
nitin.m.gupta@...cle.com, kirill.shutemov@...ux.intel.com,
dan.j.williams@...el.com, jack@...e.cz,
ross.zwisler@...ux.intel.com, jglisse@...hat.com,
willy@...radead.org, aarcange@...hat.com, oleg@...hat.com,
linux-alpha@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-snps-arc@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-ia64@...r.kernel.org,
linux-metag@...r.kernel.org, linux-mips@...ux-mips.org,
linux-parisc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
sparclinux@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.
Hi
> On 30 Mar 2018, at 10:55, Pavel Machek <pavel@....cz> wrote:
>
> Hi!
>
>> 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
Powered by blists - more mailing lists