Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp18394pxf; Tue, 16 Mar 2021 20:40:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxIV+ez0xn7Eb8aYHX+UBRm8KmniYDoBotOybK0qjsp924bSyIIXHtqPXQGmFsDSC1mxXLz X-Received: by 2002:a17:906:ca02:: with SMTP id jt2mr33131138ejb.312.1615952421875; Tue, 16 Mar 2021 20:40:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1615952421; cv=none; d=google.com; s=arc-20160816; b=LBkFMa7Q56GuTGFkqPD3kE3d5kT8DOynSjrtzpfLytI4a4rjbH89G6ek+aUqIjqLNY 7lSj+96SZmOe8xT2VaZC543OW3hnUarHpovuoWuV+D3QG3Yrzmt7l7Y234Mh7EcXNjYr +AMmF2VGSpOsmSAm4dJHM0sC7I9P8Ob9BwgqQljzoDqpYYFcjRn+KE5znvc8N3qFA7Ow 5tN4hpCTMLjLI0zwjGB8cqiV80IL/AIXj00HPZ5VwmGMgLKF9RCKFV/Hth2DFDJL4yrV UbJe0xXVxbTXiJNMa1pjuPQKxZ2cxRa7A/7/WlBvzi1pYwD2dgc4lFoZi5SPHIy6yFmZ uoKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=qiM6+yqN561ib6p2x8u0CrgYH2QK3TsVB9gl9LFtx5o=; b=RcqBSzANxLszOV7XHCz8XfC9N28Fyb9T57UPWh2qCfYjP9uobVgjun3diUNBAvDZSB WcMRcLs5duJpTebAsTVypYgTY54lr/59YuaAFu8W9EzT/qS4KvOp+mtN40tRfkD1wSpk RD686Q5kHrGfCUy52RxMmVyyZXjwxKwwh8udIc+J6vcYZy43ERQWnFwQBTrlZyRot1Fu dXoPCcMtKH1JhuSA6csb1IV5jkeh73/R32AUUM7KqBnCZmE5IvQzyQxQWlyVfKEf1PoZ Iv1pXmZPUn/Exe5TyMAfjgiWeHIYj2s21SDZVBueeOt4JYZyeZBqUftLLFEAeadKkzQk J2wA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g8si7706067ejm.240.2021.03.16.20.39.59; Tue, 16 Mar 2021 20:40:21 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230033AbhCQDi1 (ORCPT + 99 others); Tue, 16 Mar 2021 23:38:27 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:13636 "EHLO szxga04-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229492AbhCQDhy (ORCPT ); Tue, 16 Mar 2021 23:37:54 -0400 Received: from DGGEMS403-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4F0bR23lJ8z19GBh; Wed, 17 Mar 2021 11:35:58 +0800 (CST) Received: from [10.67.110.136] (10.67.110.136) by DGGEMS403-HUB.china.huawei.com (10.3.19.203) with Microsoft SMTP Server id 14.3.498.0; Wed, 17 Mar 2021 11:37:45 +0800 Subject: Re: [PATCH] powerpc: arch/powerpc/kernel/setup_64.c - cleanup warnings To: Daniel Axtens , , , , , , , , , , CC: , , References: <20210316041148.29694-1-heying24@huawei.com> <87wnu6bhvi.fsf@dja-thinkpad.axtens.net> From: "heying (H)" Message-ID: Date: Wed, 17 Mar 2021 11:37:45 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <87wnu6bhvi.fsf@dja-thinkpad.axtens.net> Content-Type: text/plain; charset="gbk"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.110.136] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thank you for your reply. ?? 2021/3/17 11:04, Daniel Axtens ะด??: > Hi He Ying, > > Thank you for this patch. > > I'm not sure what the precise rules for Fixes are, but I wonder if this > should have: > > Fixes: 9a32a7e78bd0 ("powerpc/64s: flush L1D after user accesses") > Fixes: f79643787e0a ("powerpc/64s: flush L1D on kernel entry") Is that necessary for warning cleanups? I thought 'Fixes' tags are needed only for bugfix patches. Can someone tell me whether I am right? > > Those are the commits that added the entry_flush and uaccess_flush > symbols. Perhaps one for rfi_flush too but I'm not sure what commit > introduced that. > > Kind regards, > Daniel > >> warning: symbol 'rfi_flush' was not declared. >> warning: symbol 'entry_flush' was not declared. >> warning: symbol 'uaccess_flush' was not declared. >> We found warnings above in arch/powerpc/kernel/setup_64.c by using >> sparse tool. >> >> Define 'entry_flush' and 'uaccess_flush' as static because they are not >> referenced outside the file. Include asm/security_features.h in which >> 'rfi_flush' is declared. >> >> Reported-by: Hulk Robot >> Signed-off-by: He Ying >> --- >> arch/powerpc/kernel/setup_64.c | 5 +++-- >> 1 file changed, 3 insertions(+), 2 deletions(-) >> >> diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c >> index 560ed8b975e7..f92d72a7e7ce 100644 >> --- a/arch/powerpc/kernel/setup_64.c >> +++ b/arch/powerpc/kernel/setup_64.c >> @@ -68,6 +68,7 @@ >> #include >> #include >> #include >> +#include >> >> #include "setup.h" >> >> @@ -949,8 +950,8 @@ static bool no_rfi_flush; >> static bool no_entry_flush; >> static bool no_uaccess_flush; >> bool rfi_flush; >> -bool entry_flush; >> -bool uaccess_flush; >> +static bool entry_flush; >> +static bool uaccess_flush; >> DEFINE_STATIC_KEY_FALSE(uaccess_flush_key); >> EXPORT_SYMBOL(uaccess_flush_key); >> >> -- >> 2.17.1 > .