From: "heying (H)" <heying24@huawei.com>
To: Daniel Axtens <dja@axtens.net>, <mpe@ellerman.id.au>,
<benh@kernel.crashing.org>, <paulus@samba.org>,
<npiggin@gmail.com>, <akpm@linux-foundation.org>,
<aneesh.kumar@linux.ibm.com>, <rppt@kernel.org>,
<ardb@kernel.org>, <clg@kaod.org>, <christophe.leroy@csgroup.eu>
Cc: <johnny.chenyi@huawei.com>, <linuxppc-dev@lists.ozlabs.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc: arch/powerpc/kernel/setup_64.c - cleanup warnings
Date: Wed, 17 Mar 2021 11:37:45 +0800 [thread overview]
Message-ID: <f0130916-a8f3-75ba-b5da-7d37d9139ff3@huawei.com> (raw)
In-Reply-To: <87wnu6bhvi.fsf@dja-thinkpad.axtens.net>
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 <hulkci@huawei.com>
>> Signed-off-by: He Ying <heying24@huawei.com>
>> ---
>> 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 <asm/early_ioremap.h>
>> #include <asm/pgalloc.h>
>> #include <asm/asm-prototypes.h>
>> +#include <asm/security_features.h>
>>
>> #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
> .
next prev parent reply other threads:[~2021-03-17 3:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 4:11 He Ying
2021-03-16 6:57 ` Christophe Leroy
2021-03-17 3:04 ` Daniel Axtens
2021-03-17 3:37 ` heying (H) [this message]
2021-03-17 7:58 ` Daniel Axtens
2021-03-17 11:57 ` Michael Ellerman
2021-03-18 2:37 ` heying (H)
2021-03-31 1:09 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f0130916-a8f3-75ba-b5da-7d37d9139ff3@huawei.com \
--to=heying24@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=ardb@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=dja@axtens.net \
--cc=johnny.chenyi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®