From: Mark Rutland <mark.rutland@arm.com>
To: Zhiyuan Dai <daizhiyuan@phytium.com.cn>
Cc: catalin.marinas@arm.com, will@kernel.org, Dave.Martin@arm.com,
broonie@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/kernel: minor coding style tweaks
Date: Wed, 3 Feb 2021 11:31:38 +0000 [thread overview]
Message-ID: <20210203113138.GC55896@C02TD0UTHF1T.local> (raw)
In-Reply-To: <1612329552-17977-1-git-send-email-daizhiyuan@phytium.com.cn>
On Wed, Feb 03, 2021 at 01:19:12PM +0800, Zhiyuan Dai wrote:
> Fixed two coding style issues in kernel/trap.c
> 1. spaces required around that '='
This change makes sense to me as a cleanup.
> 2. Missing a blank line after declarations
We're inconsistent w.r.t. this across the tree, and applying this
everywhere would be very churny, but I think it makes sense to be
consistent locally (e.g. within a function).
Currently call_undef_hook() is inconsistent in this respect, but I think
this patch leaves it inconsistent in a different way. Please see below.
> Signed-off-by: Zhiyuan Dai <daizhiyuan@phytium.com.cn>
> ---
> arch/arm64/kernel/traps.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index 6895ce7..4001a39 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -45,7 +45,7 @@
> #include <asm/system_misc.h>
> #include <asm/sysreg.h>
>
> -static const char *handler[]= {
> +static const char *handler[] = {
> "Synchronous Abort",
> "IRQ",
> "FIQ",
> @@ -318,6 +318,7 @@ static int call_undef_hook(struct pt_regs *regs)
> } else if (compat_thumb_mode(regs)) {
> /* 16-bit Thumb instruction */
> __le16 instr_le;
> +
> if (get_user(instr_le, (__le16 __user *)pc))
> goto exit;
> instr = le16_to_cpu(instr_le);
Immediately above this we have:
| if (!user_mode(regs)) {
| __le32 instr_le;
| if (get_kernel_nofault(instr_le, (__force __le32 *)pc))
| goto exit;
| instr = le32_to_cpu(instr_le);
... which we should either change at the same time, or not bother with
this at all.
Thanks,
Mark.
> @@ -332,6 +333,7 @@ static int call_undef_hook(struct pt_regs *regs)
> } else {
> /* 32-bit ARM instruction */
> __le32 instr_le;
> +
> if (get_user(instr_le, (__le32 __user *)pc))
> goto exit;
> instr = le32_to_cpu(instr_le);
> --
> 1.8.3.1
>
prev parent reply other threads:[~2021-02-03 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 5:19 Zhiyuan Dai
2021-02-03 11:31 ` Mark Rutland [this message]
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=20210203113138.GC55896@C02TD0UTHF1T.local \
--to=mark.rutland@arm.com \
--cc=Dave.Martin@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daizhiyuan@phytium.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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®