From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C7240C433F5 for ; Sun, 10 Oct 2021 21:39:17 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 819E960F38 for ; Sun, 10 Oct 2021 21:39:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 819E960F38 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Mime-Version:References:In-Reply-To: Message-Id:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=76d47FoGtRR9s70tmnk8r3K6uZPh1oaOEf4qmygWEUM=; b=QTNmULCmTYjVVK WjtpdHrfxfDxKKwyCe3k+l7aauOkL8QiSOCEvoMWJbHIRaw8ChYqlf3w96AWtmrMhlqxigDHryzFO bDZS8LC4RRyB2qKExqGVdc5UyVzNzk8UvaO12D3cSU2+/yK9hXvSAX8bu/zo7BBojuMvWnBuPtA/o h6leoulvQ4/zY2XBXh99lidE0zp+dElLLc5L5gQN4AV/ZNESNVkLEh8ZH0bPib5w4hTqSWKfQAd8i HAVVbiZdW8/2SX7Mey/DCl7VpL1Czq5FyiCT3LtETeqI2KYj7o3tnyxyGlJtN0BybkWnu5+LcaQ25 8gF0qSx+HRH60eaYUKGA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mZgV8-007OeI-A0; Sun, 10 Oct 2021 21:36:58 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mZgV4-007Odn-2R for linux-arm-kernel@lists.infradead.org; Sun, 10 Oct 2021 21:36:55 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id C180D610C7; Sun, 10 Oct 2021 21:36:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1633901813; bh=DufKEuJC7yYgeMY+f5psVRbO7uxiZYwbdvgx7IkVa1k=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=eFQKLwJbGwwvi6WmGCzsxmMLh0rLLHqSoB0GzNw8a3BZdxX82W5yCo6foc1IJwp/6 gypDPsALymtcVqS48Rk6xgwFD61e0kZLwI1D7/Jd4WaRNdEIGmQ1QVZ8haiFVsmxpG Ove7wxLzkj5bDnHgEu2tQ5BUU0jfgA1h5mr4VEuA= Date: Sun, 10 Oct 2021 14:36:22 -0700 From: Andrew Morton To: Kefeng Wang Cc: , , , , , , , , , , Subject: Re: [PATCH v4 0/3] arm64: support page mapping percpu first chunk allocator Message-Id: <20211010143622.18f491df5591d039cda8f7b7@linux-foundation.org> In-Reply-To: <20210910053354.26721-1-wangkefeng.wang@huawei.com> References: <20210910053354.26721-1-wangkefeng.wang@huawei.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211010_143654_170609_AFFE971C X-CRM114-Status: GOOD ( 11.86 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 10 Sep 2021 13:33:51 +0800 Kefeng Wang wrote: > Percpu embedded first chunk allocator is the firstly option, but it > could fails on ARM64, eg, > "percpu: max_distance=0x5fcfdc640000 too large for vmalloc space 0x781fefff0000" > "percpu: max_distance=0x600000540000 too large for vmalloc space 0x7dffb7ff0000" > "percpu: max_distance=0x5fff9adb0000 too large for vmalloc space 0x5dffb7ff0000" > > then we could meet "WARNING: CPU: 15 PID: 461 at vmalloc.c:3087 pcpu_get_vm_areas+0x488/0x838", > even the system could not boot successfully. > > Let's implement page mapping percpu first chunk allocator as a fallback > to the embedding allocator to increase the robustness of the system. > > Also fix a crash when both NEED_PER_CPU_PAGE_FIRST_CHUNK and KASAN_VMALLOC enabled. How serious are these problems in real-world situations? Do people feel that a -stable backport is needed, or is a 5.16-rc1 merge sufficient? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel