From: Alexandre Julliard <julliard@winehq.org>
Subject: Re: [PATCH v3 07/13] loader: Don't clobber existing memory mappings when reserving addresses.
Message-Id: <87y233yfx3.fsf@wine>
Date: Tue, 25 Jan 2022 16:48:56 +0100
In-Reply-To: <ae6c5571-7f6d-bef9-1f13-7fce210aeb62@gmail.com> (Jinoh Kang's message of "Wed, 26 Jan 2022 00:25:24 +0900")
References: <ed8913ee-6dd0-751d-3ec2-75d4865a6ed4@gmail.com> <ae6c5571-7f6d-bef9-1f13-7fce210aeb62@gmail.com>

Jinoh Kang <jinoh.kang.kr@gmail.com> writes:

> Today, the preloader makes no attempt to avoid unmapping existing
> memory mappings except the initial stack.  This results in irrevocably
> unmapping some useful preallocated memory areas, such as vDSO.
>
> Fix this by reading /proc/self/maps for existing VMAs, and splitting
> mmap() calls to avoid erasing existing memory mappings.

That defeats the purpose of using the preloader. The whole point is to
make sure the specified ranges are available. Note that since you don't
update the ranges info, the mappings will get erased by Wine later
anyway.

-- 
Alexandre Julliard
julliard@winehq.org