From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] MIPS: kprobes: Massage previous delay slot detection
Date: Tue, 10 Sep 2024 10:43:23 +0100 [thread overview]
Message-ID: <b4833f82-9e7e-4667-994b-c444ef935a9f@app.fastmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2409092259110.60835@angie.orcam.me.uk>
在2024年9月9日九月 下午11:02,Maciej W. Rozycki写道:
> On Sun, 8 Sep 2024, Jiaxun Yang wrote:
>
>> Expand the if condition into cascaded ifs to make code
>> readable.
>
> Apart from broken formatting what's making original code unreadable?
For me it's confusing because wired layout, cascaded ifs are clearly
easier to format and has clear intention.
>
>> Also use sizeof(union mips_instruction) instead of
>> sizeof(mips_instruction) to match the code context.
>
> That has to be a separate change.
Given that it's a tiny style change as well, it makes sense to combine
into same patch.
>
>> diff --git a/arch/mips/kernel/kprobes.c b/arch/mips/kernel/kprobes.c
>> index dc39f5b3fb83..96139adefad2 100644
>> --- a/arch/mips/kernel/kprobes.c
>> +++ b/arch/mips/kernel/kprobes.c
>> @@ -89,12 +89,12 @@ int arch_prepare_kprobe(struct kprobe *p)
>> goto out;
>> }
>>
>> - if (copy_from_kernel_nofault(&prev_insn, p->addr - 1,
>> - sizeof(mips_instruction)) == 0 &&
>> - insn_has_delayslot(prev_insn)) {
>> - pr_notice("Kprobes for branch delayslot are not supported\n");
>> - ret = -EINVAL;
>> - goto out;
>> + if (!copy_from_kernel_nofault(&prev_insn, p->addr - 1, sizeof(union mips_instruction))) {
>
> Overlong line.
Nowadays, check-patch.pl is happy with 100 column line.
I used 100 column line in many subsystems and never receive any complaint.
>
>> + if (insn_has_delayslot(prev_insn)) {
>> + pr_notice("Kprobes for branch delayslot are not supported\n");
>
> This now overruns 80 columns making code *less* readable.
I don't really agree, we are not in VGA display era any more, see Linus's
arguments on removal of 80 columns [1] and why long line are more readable [2].
[1]: https://lore.kernel.org/lkml/CAHk-=wj3iGQqjpvc+gf6+C29Jo4COj6OQQFzdY0h5qvYKTdCow@mail.gmail.com/
[2]: https://lore.kernel.org/lkml/CAHk-=wjR0H3+2ba0UUWwoYzYBH0GX9yTf5dj2MZyo0xvyzvJnA@mail.gmail.com/
Thanks
>
> Maciej
--
- Jiaxun
next prev parent reply other threads:[~2024-09-10 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 10:49 [PATCH 0/2] MIPS: Chore clean ups Jiaxun Yang
2024-09-08 10:49 ` [PATCH 1/2] MIPS: ftrace: Mark ftrace_get_parent_ra_addr as static Jiaxun Yang
2024-09-09 21:59 ` Maciej W. Rozycki
2024-09-08 10:49 ` [PATCH 2/2] MIPS: kprobes: Massage previous delay slot detection Jiaxun Yang
2024-09-09 22:02 ` Maciej W. Rozycki
2024-09-10 9:43 ` Jiaxun Yang [this message]
2024-09-10 10:50 ` Thomas Bogendoerfer
2024-09-10 21:03 ` Maciej W. Rozycki
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=b4833f82-9e7e-4667-994b-c444ef935a9f@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=tsbogend@alpha.franken.de \
/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