From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=47302 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PhUdA-0004AN-5C
	for qemu-devel@nongnu.org; Mon, 24 Jan 2011 17:11:25 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vapier.adi@gmail.com>) id 1PhUd8-0002Rf-Td
	for qemu-devel@nongnu.org; Mon, 24 Jan 2011 17:11:23 -0500
Received: from mail-iw0-f173.google.com ([209.85.214.173]:43196)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vapier.adi@gmail.com>) id 1PhUd8-0002RP-Op
	for qemu-devel@nongnu.org; Mon, 24 Jan 2011 17:11:22 -0500
Received: by iwn40 with SMTP id 40so4666564iwn.4
	for <qemu-devel@nongnu.org>; Mon, 24 Jan 2011 14:11:22 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <4D3DF495.8000707@gmail.com>
References: <4D3D63B3.1030402@gmail.com>
	<AANLkTin_LVqQ-BjYtyJ1YJ3C4ok2nS_E8k_HoA7TRgqG@mail.gmail.com>
	<4D3DC1F6.9030800@gmail.com>
	<AANLkTikbw-dXoRi7ETNnTRxSm+TYD4odQRjaHLrq=cX0@mail.gmail.com>
	<4D3DE7F8.6080807@gmail.com>
	<AANLkTin5Q1eiwu7HcPUE1aF7oYR9Ah3H_And2-yM=kFt@mail.gmail.com>
	<4D3DF495.8000707@gmail.com>
From: Mike Frysinger <vapier.adi@gmail.com>
Date: Mon, 24 Jan 2011 17:11:02 -0500
Message-ID: <AANLkTimw8ixTeOg93R4q1TM3=0_D9guuL-=K0AiUEJeK@mail.gmail.com>
Subject: Re: [Qemu-devel] qemu-user: relocating target code weakness
Content-Type: text/plain; charset=UTF-8
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefano Bonifazi <stefboombastic@gmail.com>
Cc: Mulyadi Santosa <mulyadi.santosa@gmail.com>, QEMU Developers <qemu-devel@nongnu.org>

On Mon, Jan 24, 2011 at 16:52, Stefano Bonifazi wrote:
>> but that can happen with the app running natively too, so any app not
>> handling MAP_FIXED failures is buggy and not qemu's problem.
>
> How? For what I learned each process executing on a OS with an mmu sees its
> virtual address space, and normally only its code is loaded there (well I am
> learning that the dynamic linker also inject into that space shared library
> code used by the process code, but of course a good dynamic linker would
> prevent clashes!)

how can the ldso possibly prevent clashes ?  it has no idea what
addresses an app will ask for at runtime.

plus, if the kernel is employing ASLR (which isnt uncommon nowadays),
the load addresses could be anywhere.
-mike