From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hoeun Ryu Subject: Re: [PATCH] mm: add VM_STATIC flag to vmalloc and prevent from removing the areas Date: Wed, 12 Apr 2017 20:42:08 +0900 Message-ID: References: <1491973350-26816-1-git-send-email-hoeun.ryu@gmail.com> <20170412060218.GA16170@infradead.org> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20170412060218.GA16170@infradead.org> Sender: owner-linux-mm@kvack.org To: Christoph Hellwig Cc: Andrew Morton , Andrey Ryabinin , Andreas Dilger , Vlastimil Babka , Michal Hocko , Chris Wilson , Ingo Molnar , zijun_hu , Matthew Wilcox , Thomas Garnier , "Kirill A. Shutemov" , linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org List-Id: linux-arch.vger.kernel.org > On Apr 12, 2017, at 3:02 PM, Christoph Hellwig wrote: >=20 >> On Wed, Apr 12, 2017 at 02:01:59PM +0900, Hoeun Ryu wrote: >> vm_area_add_early/vm_area_register_early() are used to reserve vmalloc ar= ea >> during boot process and those virtually mapped areas are never unmapped. >> So `OR` VM_STATIC flag to the areas in vmalloc_init() when importing >> existing vmlist entries and prevent those areas from being removed from t= he >> rbtree by accident. >=20 > How would they be removed "by accident"? I don't mean actual use-cases, but I just want to make it robust against lik= e programming errors. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f67.google.com ([74.125.83.67]:33944 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752179AbdDLLmL (ORCPT ); Wed, 12 Apr 2017 07:42:11 -0400 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [PATCH] mm: add VM_STATIC flag to vmalloc and prevent from removing the areas From: Hoeun Ryu In-Reply-To: <20170412060218.GA16170@infradead.org> Date: Wed, 12 Apr 2017 20:42:08 +0900 Content-Transfer-Encoding: quoted-printable Message-ID: References: <1491973350-26816-1-git-send-email-hoeun.ryu@gmail.com> <20170412060218.GA16170@infradead.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Christoph Hellwig Cc: Andrew Morton , Andrey Ryabinin , Andreas Dilger , Vlastimil Babka , Michal Hocko , Chris Wilson , Ingo Molnar , zijun_hu , Matthew Wilcox , Thomas Garnier , "Kirill A. Shutemov" , linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Message-ID: <20170412114208.CV8yeX_HHOaGMDexBtNVaj0qHkDiDnJP-SoNRUjcrcY@z> > On Apr 12, 2017, at 3:02 PM, Christoph Hellwig wrote: >=20 >> On Wed, Apr 12, 2017 at 02:01:59PM +0900, Hoeun Ryu wrote: >> vm_area_add_early/vm_area_register_early() are used to reserve vmalloc ar= ea >> during boot process and those virtually mapped areas are never unmapped. >> So `OR` VM_STATIC flag to the areas in vmalloc_init() when importing >> existing vmlist entries and prevent those areas from being removed from t= he >> rbtree by accident. >=20 > How would they be removed "by accident"? I don't mean actual use-cases, but I just want to make it robust against lik= e programming errors.