From: Joe Perches <joe@perches.com>
To: "Christophe Leroy" <christophe.leroy@c-s.fr>,
"Michal Suchánek" <msuchanek@suse.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
Michael Neuling <mikey@neuling.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/64s: Enhance the information in cpu_show_spectre_v1()
Date: Tue, 29 May 2018 09:15:21 -0700 [thread overview]
Message-ID: <0ccd6834d0c4a24f351050d0cd7581e2d2aecd7c.camel@perches.com> (raw)
In-Reply-To: <59492aa2-a12d-4f74-0a5a-14f89de64908@c-s.fr>
On Tue, 2018-05-29 at 15:24 +0000, Christophe Leroy wrote:
> On 05/29/2018 02:46 PM, Michal Suchánek wrote:
> > On Tue, 29 May 2018 16:13:49 +0200 Christophe LEROY <christophe.leroy@c-s.fr> wrote:
[]
> > diff --git a/arch/powerpc/kernel/security.c
> > > > b/arch/powerpc/kernel/security.c index 0239383c7e4d..a0c32d53980b
> > > > 100644 --- a/arch/powerpc/kernel/security.c
> > > > +++ b/arch/powerpc/kernel/security.c
> > > > @@ -120,7 +120,10 @@ ssize_t cpu_show_spectre_v1(struct device
> > > > *dev, struct device_attribute *attr, c if
> > > > (!security_ftr_enabled(SEC_FTR_BNDS_CHK_SPEC_BAR)) return
> > > > sprintf(buf, "Not affected\n");
> > > > - return sprintf(buf, "Vulnerable\n");
> > > > + if (barrier_nospec_enabled)
> > > > + return sprintf(buf, "Mitigation: __user pointer
> > > > sanitization\n");
> > > > + else
> > > > + return sprintf(buf, "Vulnerable\n");
> > >
> > > Checkpatch would tell you that an else is unneeded after a return. So
> > > just leave it as it was before.
> >
> > Where did you get your copy of checkpatch? The one in Linux tree does
> > not do that.
Correct as this particular style is a maintainer preference.
> Strange, it should, as checkpatch.pl includes the following code:
>
> # check indentation of any line with a bare else
> # (but not if it is a multiple line "if (foo) return bar; else return baz;")
Note this comment and also that this case is
if (foo)
return bar;
else
return baz;
so no warning is generated.
> # if the previous line is a break or return and is indented 1 tab more...
> if ($sline =~ /^\+([\t]+)(?:}[ \t]*)?else(?:[ \t]*{)?\s*$/) {
> my $tabs = length($1) + 1;
> if ($prevline =~ /^\+\t{$tabs,$tabs}break\b/ ||
> ($prevline =~ /^\+\t{$tabs,$tabs}return\b/ &&
> defined $lines[$linenr] &&
> $lines[$linenr] !~ /^[ \+]\t{$tabs,$tabs}return/)) {
> WARN("UNNECESSARY_ELSE",
> "else is not generally useful after a break or return\n" .
> $hereprev);
> }
> }
>
>
> Anyway, you should remove that 'else' in your patch.
> And the other sprintf line is over 80 characters.
>
> Christophe
>
> >
> > Thanks
> >
> > Michal
> >
next prev parent reply other threads:[~2018-05-29 16:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 4:15 [PATCH 1/6] powerpc/64s: Add barrier_nospec Michael Ellerman
2018-04-24 4:15 ` [PATCH 2/6] powerpc/64s: Add support for ori barrier_nospec patching Michael Ellerman
2018-04-26 16:10 ` Michal Suchánek
2018-05-01 12:25 ` Michael Ellerman
2018-04-24 4:15 ` [PATCH 3/6] powerpc/64s: Patch barrier_nospec in modules Michael Ellerman
2018-05-03 13:15 ` Michal Suchánek
2018-04-24 4:15 ` [PATCH 4/6] powerpc/64s: Enable barrier_nospec based on firmware settings Michael Ellerman
2018-04-26 16:02 ` Michal Suchánek
2018-05-01 11:11 ` Michael Ellerman
2018-05-02 11:41 ` Michal Suchánek
2018-05-04 0:58 ` Michael Ellerman
2018-04-24 4:15 ` [PATCH 5/6] powerpc: Use barrier_nospec in copy_from_user() Michael Ellerman
2018-04-24 4:15 ` [PATCH 6/6] powerpc/64: Use barrier_nospec in syscall entry Michael Ellerman
2018-04-24 5:44 ` [PATCH 1/6] powerpc/64s: Add barrier_nospec Nicholas Piggin
2018-05-28 13:19 ` [PATCH] powerpc/64s: Enhance the information in cpu_show_spectre_v1() Michal Suchanek
2018-05-29 14:03 ` kbuild test robot
2018-05-29 14:13 ` Christophe LEROY
2018-05-29 14:46 ` Michal Suchánek
2018-05-29 15:24 ` Christophe Leroy
2018-05-29 16:15 ` Joe Perches [this message]
2018-06-04 14:11 ` Michael Ellerman
2018-06-04 14:10 ` [1/6] powerpc/64s: Add barrier_nospec 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=0ccd6834d0c4a24f351050d0cd7581e2d2aecd7c.camel@perches.com \
--to=joe@perches.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mauricfo@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=msuchanek@suse.de \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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®