Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3998398ybz; Mon, 20 Apr 2020 13:31:16 -0700 (PDT) X-Google-Smtp-Source: APiQypKoyKie5vK1pkyd6BnGSUFZpHlvf0swX+M6PhBGFCZGXoRZTAONv4EzdjdxYtNBdHrFnpeL X-Received: by 2002:a17:906:7ac8:: with SMTP id k8mr18224420ejo.235.1587414676426; Mon, 20 Apr 2020 13:31:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587414676; cv=none; d=google.com; s=arc-20160816; b=qVdDuV1RAh8r0rGSBsJmKatU+Hz0MAubbaFQ3xQfqf/oP4oo/u/CgBx5v7W2ao1Cfy c1lWTwsZwSKq/CrnscJCXe9lKsjyjIgeIrHHCfDYGtu3q7Q10GftqE5fxjViOQrlPnDp y6ABz2NxioBdW7pQ0gKurCN+MB52bfrXLMZj0GXhFvPNVeZ9Hkq3BU1If0pWzetfa4Gz XEi/qDH+DPaxriA8p5vBBbHvjev7NY+GBtLOBdhM+CWuyC7azkoOyg3PLuaE9j3I+BTy isYwlMBtegaM5Ucb57pS1o2pMfFY4lQmNvXj5YZISGvhP48tp8gDl6Ys0LFo1cW/WSyG y1BQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=wlD7exmpP2wJ9RvD3qhW6lLoxeeNIloAY3kkOGxGrPg=; b=EP6W6G8M5PtNPloHU29pfQ0b8A3u0kn5SLG+HTdnLq4HxkEoI+g/CXv7S2WHvar+fo 6wCUZ9t3kL8D2RiRKn5kXzINiFAgbg3wTKkpziRAnvrZ5frtW6d+VeNmCLB+h+aSohvG 0+4c2rXhzEXTTkVHJaTnfviL6QONvNfdn2e/0DzwZFfh2bRaYv0c5vyxh/w4Y6xugUDf MHXfpsFNJsRsLQCG85iInZw9Tw2dxaH/NjbpmaWhbS+GtLYfPrLX5VBeeRcrkbBh9IJD lZjDTbuMKTeUQuFyPAm62xj4nT/RnoNZL7qyw7upLNBu1RmGAn4SFnZTAiPfeA7QX7Lb gY/A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=CSrYF4gw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d2si246942edo.472.2020.04.20.13.30.52; Mon, 20 Apr 2020 13:31:16 -0700 (PDT) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=CSrYF4gw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725958AbgDTU3y (ORCPT + 99 others); Mon, 20 Apr 2020 16:29:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50592 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726055AbgDTU3x (ORCPT ); Mon, 20 Apr 2020 16:29:53 -0400 Received: from mail-lf1-x141.google.com (mail-lf1-x141.google.com [IPv6:2a00:1450:4864:20::141]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3823BC061A0E for ; Mon, 20 Apr 2020 13:29:53 -0700 (PDT) Received: by mail-lf1-x141.google.com with SMTP id 198so9183418lfo.7 for ; Mon, 20 Apr 2020 13:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wlD7exmpP2wJ9RvD3qhW6lLoxeeNIloAY3kkOGxGrPg=; b=CSrYF4gwenMWMaslCcQijRCNO9eq1UfvXXSV8pttbEiArbr/aQ0aFZA3NJEU462YCW ta5FSBuZKNh3DjHJ9A+mTPvAqqcxx8gsP38e2aO+vWiQFGoU+OZBQPi5EAKOFGJQ9FJj Vj0bLG8tDjADXIf3/IHx2bOqwK0ghVn+Kk1WRa2/rhWY7yuPOAVIzb8+OB+1AXr7/mDV nPN9r/51dJd8TEtzmYhidX88xsTU+niNazjYNoDQ5+L3ER1iCQuriV+bIdRjpF61vIIh PYP3+KLT6Gdt17ScXYNgHxdjm+9KFieAZARtrDpZtitChEwJQ6XlOk4yvS9U0YGCd6pb P9Nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wlD7exmpP2wJ9RvD3qhW6lLoxeeNIloAY3kkOGxGrPg=; b=PlZ0pIeCINJBgFnjvESVkmBOFHrZfxXUSbCAM2M6tB10gaXaEpjcgLAVwxEBgqCfWr qdJUyVsjWUUvxnZFUFvbej5e1X2rTGTeMfLEoKPJlhedSeXyY3ChUGuEfNCxXoLuvuzc 00bcGbGhnClwLa8HSUe7+rLC2Y7nA0IEQ2v+1a8IG+OBfBhaoFDDQwgh4A09jI7+3Ocy /F8Lt9ri905Fdt3w1/cml5ytqQxdwYixTqvuXaPvHiZ9EVwZyAlau0MhEB2pRbF+7JHz nYiQbW3kuT7GcB4ucka3k0DFRJmhTTT8m1U8gwx6JQZ+e9ana3MwGj58+QbFO8TGpFm9 21Aw== X-Gm-Message-State: AGi0PubOMtqmhPWudePC1i6fWiwZ4Q08kL7W0yUA6JbDRO7hr17dpiRn S5rA88yDKvrLrW5tz/+yLejO2W6frdR388VA25tTaQ== X-Received: by 2002:a05:6512:1109:: with SMTP id l9mr11730849lfg.12.1587414591448; Mon, 20 Apr 2020 13:29:51 -0700 (PDT) MIME-Version: 1.0 References: <20200417185049.275845-1-mike.kravetz@oracle.com> <5E312000-05D8-4C5D-A7C0-DDDE1842CB0E@lca.pw> <4c36c6ce-3774-78fa-abc4-b7346bf24348@oracle.com> In-Reply-To: <4c36c6ce-3774-78fa-abc4-b7346bf24348@oracle.com> From: Anders Roxell Date: Mon, 20 Apr 2020 22:29:40 +0200 Message-ID: Subject: Re: [PATCH v3 0/4] Clean up hugetlb boot command line processing To: Mike Kravetz Cc: Qian Cai , Linux-MM , LKML , Linux ARM , linuxppc-dev , linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, sparclinux@vger.kernel.org, linux-doc@vger.kernel.org, Catalin Marinas , Will Deacon , Benjamin Herrenschmidt , Paul Mackerras , Paul Walmsley , Palmer Dabbelt , Albert Ou , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , "David S.Miller" , Thomas Gleixner , Ingo Molnar , Dave Hansen , Jonathan Corbet , Longpeng , Christophe Leroy , Randy Dunlap , Mina Almasry , Peter Xu , Nitesh Narayan Lal , Andrew Morton Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 20 Apr 2020 at 20:23, Mike Kravetz wrote: > > On 4/20/20 8:34 AM, Qian Cai wrote: > > > > > >> On Apr 17, 2020, at 2:50 PM, Mike Kravetz wrote: > >> > >> Longpeng(Mike) reported a weird message from hugetlb command line processing > >> and proposed a solution [1]. While the proposed patch does address the > >> specific issue, there are other related issues in command line processing. > >> As hugetlbfs evolved, updates to command line processing have been made to > >> meet immediate needs and not necessarily in a coordinated manner. The result > >> is that some processing is done in arch specific code, some is done in arch > >> independent code and coordination is problematic. Semantics can vary between > >> architectures. > >> > >> The patch series does the following: > >> - Define arch specific arch_hugetlb_valid_size routine used to validate > >> passed huge page sizes. > >> - Move hugepagesz= command line parsing out of arch specific code and into > >> an arch independent routine. > >> - Clean up command line processing to follow desired semantics and > >> document those semantics. > >> > >> [1] https://lore.kernel.org/linux-mm/20200305033014.1152-1-longpeng2@huawei.com > >> > >> Mike Kravetz (4): > >> hugetlbfs: add arch_hugetlb_valid_size > >> hugetlbfs: move hugepagesz= parsing to arch independent code > >> hugetlbfs: remove hugetlb_add_hstate() warning for existing hstate > >> hugetlbfs: clean up command line processing > > > > Reverted this series fixed many undefined behaviors on arm64 with the config, > > > > https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config > > > > [ 54.172683][ T1] UBSAN: shift-out-of-bounds in ./include/linux/hugetlb.h:555:34 > > [ 54.180411][ T1] shift exponent 4294967285 is too large for 64-bit type 'unsigned long' > > [ 54.188885][ T1] CPU: 130 PID: 1 Comm: swapper/0 Not tainted 5.7.0-rc2-next-20200420 #1 > > [ 54.197284][ T1] Hardware name: HPE Apollo 70 /C01_APACHE_MB , BIOS L50_5.13_1.11 06/18/2019 > > [ 54.207888][ T1] Call trace: > > [ 54.211100][ T1] dump_backtrace+0x0/0x224 > > [ 54.215565][ T1] show_stack+0x20/0x2c > > [ 54.219651][ T1] dump_stack+0xfc/0x184 > > [ 54.223829][ T1] __ubsan_handle_shift_out_of_bounds+0x304/0x344 > > [ 54.230204][ T1] hugetlb_add_hstate+0x3ec/0x414 > > huge_page_size at include/linux/hugetlb.h:555 > > (inlined by) hugetlb_add_hstate at mm/hugetlb.c:3301 > > [ 54.235191][ T1] hugetlbpage_init+0x14/0x30 > > [ 54.239824][ T1] do_one_initcall+0x6c/0x144 > > [ 54.244446][ T1] do_initcall_level+0x158/0x1c4 > > [ 54.249336][ T1] do_initcalls+0x68/0xb0 > > [ 54.253597][ T1] do_basic_setup+0x28/0x30 > > [ 54.258049][ T1] kernel_init_freeable+0x19c/0x228 > > [ 54.263188][ T1] kernel_init+0x14/0x208 > > [ 54.267473][ T1] ret_from_fork+0x10/0x18 > > While rearranging the code (patch 3 in series), I made the incorrect > assumption that CONT_XXX_SIZE == (1UL << CONT_XXX_SHIFT). However, > this is not the case. Does the following patch fix these issues? > > From b75cb4a0852e208bee8c4eb347dc076fcaa88859 Mon Sep 17 00:00:00 2001 > From: Mike Kravetz > Date: Mon, 20 Apr 2020 10:41:18 -0700 > Subject: [PATCH] arm64/hugetlb: fix hugetlb initialization > > When calling hugetlb_add_hstate() to initialize a new hugetlb size, > be sure to use correct huge pages size order. > > Signed-off-by: Mike Kravetz > --- > arch/arm64/mm/hugetlbpage.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/arch/arm64/mm/hugetlbpage.c b/arch/arm64/mm/hugetlbpage.c > index 9ca840527296..a02411a1f19a 100644 > --- a/arch/arm64/mm/hugetlbpage.c > +++ b/arch/arm64/mm/hugetlbpage.c > @@ -453,11 +453,11 @@ void huge_ptep_clear_flush(struct vm_area_struct *vma, > static int __init hugetlbpage_init(void) > { > #ifdef CONFIG_ARM64_4K_PAGES > - hugetlb_add_hstate(PUD_SHIFT - PAGE_SHIFT); > + hugetlb_add_hstate(ilog2(PUD_SIZE) - PAGE_SHIFT); > #endif > - hugetlb_add_hstate(CONT_PMD_SHIFT - PAGE_SHIFT); > - hugetlb_add_hstate(PMD_SHIFT - PAGE_SHIFT); > - hugetlb_add_hstate(CONT_PTE_SHIFT - PAGE_SHIFT); > + hugetlb_add_hstate(ilog2(CONT_PMD_SIZE) - PAGE_SHIFT); > + hugetlb_add_hstate(ilog2(PMD_SIZE) - PAGE_SHIFT); > + hugetlb_add_hstate(ilog2(CONT_PTE_SIZE) - PAGE_SHIFT); > > return 0; > } I build this for an arm64 kernel and ran it in qemu and it worked. Cheers, Anders