[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4f5eb24c-5af2-eebf-d54f-875f4b259793@oracle.com>
Date: Mon, 27 Nov 2017 08:51:10 -0700
From: Khalid Aziz <khalid.aziz@...cle.com>
To: Michal Hocko <mhocko@...nel.org>, linux-api@...r.kernel.org
Cc: Michael Ellerman <mpe@...erman.id.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Andrea Arcangeli <aarcange@...hat.com>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org,
Abdul Haleem <abdhalee@...ux.vnet.ibm.com>,
Joel Stanley <joel@....id.au>,
Kees Cook <keescook@...omium.org>
Subject: Re: [RFC PATCH 0/2] mm: introduce MAP_FIXED_SAFE
On 11/24/2017 01:54 AM, Michal Hocko wrote:
> Are there any more concerns? So far the biggest one was the name. The
> other which suggests a flag as a modifier has been sorted out hopefully.
> Is there anymore more before we can consider this for merging? Well
> except for man page update which I will prepare of course. Can we target
> this to 4.16?
I do not have concerns with this approach. I prefer a new flag as
opposed to a modifier and the name is ok by me.
Reviewed-by: Khalid Aziz <khalid.aziz@...cle.com>
Powered by blists - more mailing lists