From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751793AbdJTGmA (ORCPT <rfc822;w@1wt.eu>);
        Fri, 20 Oct 2017 02:42:00 -0400
Received: from mail.cn.fujitsu.com ([183.91.158.132]:21334 "EHLO
        heian.cn.fujitsu.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org
        with ESMTP id S1751193AbdJTGl7 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 20 Oct 2017 02:41:59 -0400
X-IronPort-AV: E=Sophos;i="5.43,368,1503331200"; 
   d="scan'208";a="29406106"
Subject: Re: [PATCH 0/4] kaslr: extend movable_node to
 movable_node=nn[KMG]@ss[KMG]
To: Chao Fan <fanc.fnst@cn.fujitsu.com>
References: <20171019100243.25259-1-fanc.fnst@cn.fujitsu.com>
 <900bb043-527b-94ce-da11-7a98f8352150@cn.fujitsu.com>
 <20171020025321.GD17909@localhost.localdomain>
 <0399dc49-6293-cc4e-cbff-e267efca7407@cn.fujitsu.com>
 <20171020034614.GD5635@localhost.localdomain>
CC: <linux-kernel@vger.kernel.org>, <x86@kernel.org>, <hpa@zytor.com>,
        <tglx@linutronix.de>, <mingo@redhat.com>, <bhe@redhat.com>,
        <keescook@chromium.org>, <indou.takao@jp.fujitsu.com>,
        <caoj.fnst@cn.fujitsu.com>
From: Dou Liyang <douly.fnst@cn.fujitsu.com>
Message-ID: <cf340654-39e2-af23-ef9a-156d097a6290@cn.fujitsu.com>
Date: Fri, 20 Oct 2017 14:41:53 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <20171020034614.GD5635@localhost.localdomain>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.167.226.106]
X-yoursite-MailScanner-ID: 4301847F13D1.A8C40
X-yoursite-MailScanner: Found to be clean
X-yoursite-MailScanner-From: douly.fnst@cn.fujitsu.com
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Chao,

[...]
>
> Thanks for that. I think likely() is suitable for another place.

Aha, Just as an example, don't need to use it. ;-)

>>>
>>> Both are OK. I think outputing the memory region in movable_node or
>>> immovable_node are both reasonable. So the interface of both methods
>>> will be useful. And after we decided which policy used in kaslr, then
>>> add the interface of /sys.

Yes, so great.

>>>
>>
>> Actually, I prefer the first one, are you ready to post the patches
>> for the first policy?
>>

I guess you may miss this, I want to know if you have already do the
first policy. then we can compare and decide which one is better. If
not, I can do that! let's make KASLR work well with node hot-plug
quickly.

cc Baoquan,

do you have any ideas, ;-)

Thanks,
	dou.