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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id AB6FCCD11C2 for ; Fri, 5 Apr 2024 09:53:42 +0000 (UTC) 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=+QQ5eaFf8mkj79Pss8d45Q/X6C6I4J/LuRBdYIjyVcQ=; b=lULG0zgtKwlopj lmst0L4rG3mLm6NfiWJInF3L7mR+9gnp1TNOdHCM+NaIPyprW5e1++YZ+caVuKFi+xUZlZstVAaq4 5DyfWiEkRJ5qNZpsHD50jQ4l5vqALEy88z4x5hTjhH0OJajuaiUQhe7qlzTFSG+wdJpR8kfcwXRgf G/GB6O1Pq08JhqRTKDl2HBtgAUxm6J/Yl2NasSvB+GNtO8Jpw5syWAhuwjBYx6zroq6H+jLZk8v7n +SLDW+wGo/vf5kBTrCETwSWwPjmm14tdDOt9y9tzw5CI/wZ4Fx33A8Mnm6IKwNbrdrJ+EehVbsP4v Akg9Sa7rLB6rYTrGI7wA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rsgGK-00000006HMg-1Bs7; Fri, 05 Apr 2024 09:53:32 +0000 Received: from frasgout.his.huawei.com ([185.176.79.56]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rsgGH-00000006HLD-2QnC for linux-arm-kernel@lists.infradead.org; Fri, 05 Apr 2024 09:53:31 +0000 Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4V9v0P2GBxz6J6c8; Fri, 5 Apr 2024 17:52:05 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (unknown [7.191.163.240]) by mail.maildlp.com (Postfix) with ESMTPS id 963691400D1; Fri, 5 Apr 2024 17:53:27 +0800 (CST) Received: from localhost (10.202.227.76) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Fri, 5 Apr 2024 10:53:27 +0100 Date: Fri, 5 Apr 2024 10:53:26 +0100 From: Jonathan Cameron To: Mark Rutland CC: Dawei Li , , , , , , , , , , , Subject: Re: [PATCH v2 08/10] perf/hisi_uncore: Avoid placing cpumask var on stack Message-ID: <20240405105326.000039e2@Huawei.com> In-Reply-To: References: <20240403125109.2054881-1-dawei.li@shingroup.cn> <20240403125109.2054881-9-dawei.li@shingroup.cn> Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) MIME-Version: 1.0 X-Originating-IP: [10.202.227.76] X-ClientProxiedBy: lhrpeml100003.china.huawei.com (7.191.160.210) To lhrpeml500005.china.huawei.com (7.191.163.240) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240405_025329_829686_7296C627 X-CRM114-Status: GOOD ( 16.42 ) 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 Wed, 3 Apr 2024 15:35:47 +0100 Mark Rutland wrote: > On Wed, Apr 03, 2024 at 08:51:07PM +0800, Dawei Li wrote: > > For CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask > > variable on stack is not recommended since it can cause potential stack > > overflow. > > > > Instead, kernel code should always use *cpumask_var API(s) to allocate > > cpumask var in config-neutral way, leaving allocation strategy to > > CONFIG_CPUMASK_OFFSTACK. > > > > But dynamic allocation in cpuhp's teardown callback is somewhat problematic > > for if allocation fails(which is unlikely but still possible): > > - If -ENOMEM is returned to caller, kernel crashes for non-bringup > > teardown; > > - If callback pretends nothing happened and returns 0 to caller, it may > > trap system into an in-consisitent/compromised state; > > > > Use newly-introduced cpumask_any_and_but() to address all issues above. > > It eliminates usage of temporary cpumask var in generic way, no matter how > > the cpumask var is allocated. > > > > Suggested-by: Mark Rutland > > Signed-off-by: Dawei Li > > The logic looks good to me, but I'd like the commit message updated the same as > per my comment on patch 2. > > With that commit message: > > Reviewed-by: Mark Rutland Acked-by: Jonathan Cameron _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel