From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752162AbcEJSVG (ORCPT ); Tue, 10 May 2016 14:21:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40882 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751485AbcEJSVD (ORCPT ); Tue, 10 May 2016 14:21:03 -0400 Date: Tue, 10 May 2016 20:20:55 +0200 From: Oleg Nesterov To: Andy Lutomirski Cc: Dmitry Safonov <0x7f454c46@gmail.com>, Ruslan Kabatsayev , X86 ML , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , Borislav Petkov , Pavel Emelyanov , Cyrill Gorcunov Subject: Re: Getting rid of dynamic TASK_SIZE (on x86, at least) Message-ID: <20160510182055.GA24868@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 10 May 2016 18:21:03 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/10, Andy Lutomirski wrote: > > - xol_add_vma: This one is weird: uprobes really is doing something > behind the task's back, and the addresses need to be consistent with > the address width. I'm not quite sure what to do here. It can use mm->task_size instead, plus this is just a hint. And perhaps mm->task_size should have more users, say get_unmapped_area... Not sure we should really get rid of dynamic TASK_SIZE completely, but personally I agree it looks a bit ugly. Oleg.