Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 5 Oct 2020 08:12:10 -0600
From:   Jonathan Corbet <corbet@lwn.net>
To:     Topi Miettinen <toiwoton@gmail.com>
Cc:     Michal Hocko <mhocko@suse.com>,
        David Hildenbrand <david@redhat.com>,
        akpm@linux-foundation.org, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: optionally disable brk()
Message-ID: <20201005081210.2231e552@lwn.net>
In-Reply-To: <7d7b1ac5-d6a7-5e43-8fb8-12b844d7f501@gmail.com>
References: <20201002171921.3053-1-toiwoton@gmail.com>
        <653873ef-2a57-37e0-1ac3-fba763652b35@redhat.com>
        <2a0f5ade-d770-c36e-50bc-ff0c8e9dacbf@gmail.com>
        <20201005061248.GN4555@dhcp22.suse.cz>
        <7d7b1ac5-d6a7-5e43-8fb8-12b844d7f501@gmail.com>
Organization: LWN.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 5 Oct 2020 11:11:35 +0300
Topi Miettinen <toiwoton@gmail.com> wrote:

> The point is not to shrink the kernel (it will shrink by one small 
> function) or get rid of complexity. The point is to disable an inferior 
> interface. Memory returned by mmap() is at a random location but with 
> brk() it is located near the data segment, so the address is more easily 
> predictable.

So if your true objective is to get glibc to allocate memory differently,
perhaps the right thing to do is to patch glibc?

Thanks,

jon