From: Masami Hiramatsu <mhiramat@kernel.org>
To: X86 ML <x86@kernel.org>, Ingo Molnar <mingo@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>, Daniel Xu <dxu@dxuuu.xyz>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
kuba@kernel.org, mingo@redhat.com, ast@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
kernel-team@fb.com, yhs@fb.com, linux-ia64@vger.kernel.org,
Abhishek Sagar <sagar.abhishek@gmail.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: [PATCH -tip 0/6] kprobes: treewide: Clean up kprobe code
Date: Sat, 10 Jul 2021 23:55:19 +0900 [thread overview]
Message-ID: <162592891873.1158485.768824457210707916.stgit@devnote2> (raw)
Hi Ingo,
Here is a series of patches to cleanup the kprobes code. I tried to fix
error message issues, comments, checkpatch.pl issues and so on. Some
of those are what you suggested and pointed in the x86 stacktrace series.
https://lore.kernel.org/bpf/YOK39GTuueIDeaJL@gmail.com/
I decided to split this seires from the x86 stacktrace fix series because
there still be some on going discussions on that thread. The stacktrace
fix series will be rebased on this series (and I've almost done, except
for some discussion items).
Since this is a cleanup series, this does not change any functionality
(of course some error messages, warnings, lock assertions are chaneged)
but the coding styles are improved. I will continue this cleanup activities
for each architecture port, and rethink the internal coding design and
interfaces too.
Thank you,
---
Masami Hiramatsu (6):
kprobes: treewide: Cleanup the error messages for kprobes
kprobes: Fix coding style issues
kprobes: Use IS_ENABLED() instead of kprobes_built_in()
kprobes: Add assertions for required lock
kprobes: treewide: Use 'kprobe_opcode_t *' for the code address in get_optimized_kprobe()
kprobes: Use bool type for functions which returns boolean value
arch/arm/probes/kprobes/core.c | 4
arch/arm/probes/kprobes/opt-arm.c | 7 -
arch/arm64/kernel/probes/kprobes.c | 5 -
arch/csky/kernel/probes/kprobes.c | 10 +
arch/mips/kernel/kprobes.c | 11 +
arch/powerpc/kernel/optprobes.c | 6 -
arch/riscv/kernel/probes/kprobes.c | 11 +
arch/s390/kernel/kprobes.c | 4
arch/x86/kernel/kprobes/opt.c | 6 -
include/linux/kprobes.h | 64 +++----
kernel/kprobes.c | 315 +++++++++++++++++++-----------------
11 files changed, 226 insertions(+), 217 deletions(-)
--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
next reply other threads:[~2021-07-10 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 14:55 Masami Hiramatsu [this message]
2021-07-10 14:55 ` [PATCH -tip 1/6] kprobes: treewide: Cleanup the error messages for kprobes Masami Hiramatsu
2021-07-10 14:55 ` [PATCH -tip 2/6] kprobes: Fix coding style issues Masami Hiramatsu
2021-07-10 14:55 ` [PATCH -tip 3/6] kprobes: Use IS_ENABLED() instead of kprobes_built_in() Masami Hiramatsu
2021-07-10 14:55 ` [PATCH -tip 4/6] kprobes: Add assertions for required lock Masami Hiramatsu
2021-07-10 14:56 ` [PATCH -tip 5/6] kprobes: treewide: Use 'kprobe_opcode_t *' for the code address in get_optimized_kprobe() Masami Hiramatsu
2021-07-10 14:56 ` [PATCH -tip 6/6] kprobes: Use bool type for functions which returns boolean value Masami Hiramatsu
2021-07-10 16:27 ` Joe Perches
2021-07-11 1:26 ` Masami Hiramatsu
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=162592891873.1158485.768824457210707916.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=jpoimboe@redhat.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sagar.abhishek@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yhs@fb.com \
/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;
as well as URLs for NNTP newsgroup(s).