Re: [PATCH] Document randomize_va_space and CONFIG_COMPAT_BRK (was Re: [PATCH 2/2] ASLR: add possibility for more fine-grained tweaking)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Ingo Molnar <mingo@...>
Cc: Andrew Morton <akpm@...>, Arjan van de Ven <arjan@...>, Randy Dunlap <randy.dunlap@...>, Hugh Dickins <hugh@...>, Pavel Machek <pavel@...>, <linux-kernel@...>
Date: Thursday, February 7, 2008 - 10:30 am

On Thu, 7 Feb 2008, Ingo Molnar wrote:


So what do you think is proper behavior in situation when 
CONFIG_COMPAT_BRK=N on 64bit kernel, and 32bit-binary is loaded in 32bit 
emulation?

We can either leave the brk as-is, but that is in contradiction to user 
explictly specifying CONFIG_COMPAT_BRK=N. Is this what you propose?

Or we can randomize brk start in such situation, but that is the behavior 
we currently automatically have due to CONFIG_COMPAT_BRK=N, so no change 
is needed.

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 0/2] brk and randomization fixes, Jiri Kosina, (Wed Feb 6, 9:45 am)
Re: [PATCH 2/2] ASLR: add possibility for more fine-grained ..., Geert Uytterhoeven, (Thu Feb 7, 6:23 am)
Re: [PATCH 2/2] ASLR: add possibility for more fine-grained ..., Geert Uytterhoeven, (Thu Feb 7, 6:43 am)
Re: [PATCH] Document randomize_va_space and CONFIG_COMPAT_BR..., Jiri Kosina, (Thu Feb 7, 10:30 am)
[PATCH 1/2] brk: check the lower bound properly, Jiri Kosina, (Wed Feb 6, 9:45 am)