From: Ze Gao <zegao2021@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Heiko Carstens <hca@linux.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Sven Schnelle <svens@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vasily Gorbik <gor@linux.ibm.com>,
x86@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Conor Dooley <conor@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Yonghong Song <yhs@fb.com>, Ze Gao <zegao@tencent.com>
Subject: [PATCH v3 0/3] Make fprobe + rethook immune to recursion
Date: Wed, 17 May 2023 11:45:05 +0800 [thread overview]
Message-ID: <20230517034510.15639-1-zegao@tencent.com> (raw)
Hi all,
This is the 3rd version of patch series that fix the ftrace rethook recursion problem.
Changes since v2:
- refine commit message of [PATCH v2 2/4] fprobe: make fprobe_kprobe_handler recursion free
v1: https://lore.kernel.org/linux-trace-kernel/cover.1684120990.git.zegao@tencent.com/T/
v2: https://lore.kernel.org/linux-trace-kernel/ZGP4ypidaxQGdp7Y@krava/T/#mb9e74fe74d5800ee424234b26c6def9d5135237b
The original discussions of this bug can be checked out here:
https://lore.kernel.org/bpf/CAD8CoPCfPmqZH6BJCk3Y1-02BLVVsbQ6OeaNOhcfGWmdF0oX8A@mail.gmail.com/T/#t
Ze Gao (4):
rethook: use preempt_{disable, enable}_notrace in
rethook_trampoline_handler
fprobe: make fprobe_kprobe_handler recursion free
fprobe: add recursion detection in fprobe_exit_handler
rethook, fprobe: do not trace rethook related functions
arch/riscv/kernel/probes/Makefile | 2 +
arch/s390/kernel/Makefile | 1 +
arch/x86/kernel/Makefile | 1 +
kernel/trace/fprobe.c | 73 ++++++++++++++++++++++++-------
kernel/trace/rethook.c | 4 +-
5 files changed, 64 insertions(+), 17 deletions(-)
--
2.40.1
WARNING: multiple messages have this Message-ID (diff)
From: Ze Gao <zegao2021@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Heiko Carstens <hca@linux.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Sven Schnelle <svens@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vasily Gorbik <gor@linux.ibm.com>,
x86@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Conor Dooley <conor@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Yonghong Song <yhs@fb.com>, Ze Gao <zegao@tencent.com>
Subject: [PATCH v3 0/3] Make fprobe + rethook immune to recursion
Date: Wed, 17 May 2023 11:45:05 +0800 [thread overview]
Message-ID: <20230517034510.15639-1-zegao@tencent.com> (raw)
Hi all,
This is the 3rd version of patch series that fix the ftrace rethook recursion problem.
Changes since v2:
- refine commit message of [PATCH v2 2/4] fprobe: make fprobe_kprobe_handler recursion free
v1: https://lore.kernel.org/linux-trace-kernel/cover.1684120990.git.zegao@tencent.com/T/
v2: https://lore.kernel.org/linux-trace-kernel/ZGP4ypidaxQGdp7Y@krava/T/#mb9e74fe74d5800ee424234b26c6def9d5135237b
The original discussions of this bug can be checked out here:
https://lore.kernel.org/bpf/CAD8CoPCfPmqZH6BJCk3Y1-02BLVVsbQ6OeaNOhcfGWmdF0oX8A@mail.gmail.com/T/#t
Ze Gao (4):
rethook: use preempt_{disable, enable}_notrace in
rethook_trampoline_handler
fprobe: make fprobe_kprobe_handler recursion free
fprobe: add recursion detection in fprobe_exit_handler
rethook, fprobe: do not trace rethook related functions
arch/riscv/kernel/probes/Makefile | 2 +
arch/s390/kernel/Makefile | 1 +
arch/x86/kernel/Makefile | 1 +
kernel/trace/fprobe.c | 73 ++++++++++++++++++++++++-------
kernel/trace/rethook.c | 4 +-
5 files changed, 64 insertions(+), 17 deletions(-)
--
2.40.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-05-17 3:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 3:45 Ze Gao [this message]
2023-05-17 3:45 ` [PATCH v3 0/3] Make fprobe + rethook immune to recursion Ze Gao
2023-05-17 3:45 ` [PATCH v3 1/4] rethook: use preempt_{disable, enable}_notrace in rethook_trampoline_handler Ze Gao
2023-05-17 3:45 ` Ze Gao
2023-05-17 11:59 ` Masami Hiramatsu
2023-05-17 11:59 ` Masami Hiramatsu
2023-05-18 2:40 ` Ze Gao
2023-05-18 2:40 ` Ze Gao
2023-05-17 3:45 ` [PATCH v3 2/4] fprobe: make fprobe_kprobe_handler recursion free Ze Gao
2023-05-17 3:45 ` Ze Gao
2023-05-17 10:47 ` Jiri Olsa
2023-05-17 10:47 ` Jiri Olsa
2023-05-17 11:42 ` Masami Hiramatsu
2023-05-17 11:42 ` Masami Hiramatsu
2023-05-17 12:30 ` Jiri Olsa
2023-05-17 12:30 ` Jiri Olsa
2023-05-17 14:27 ` Masami Hiramatsu
2023-05-17 14:27 ` Masami Hiramatsu
2023-05-18 0:16 ` Andrii Nakryiko
2023-05-18 0:16 ` Andrii Nakryiko
2023-05-18 2:49 ` Ze Gao
2023-05-18 2:49 ` Ze Gao
2023-06-28 7:16 ` Yafang Shao
2023-06-28 7:16 ` Yafang Shao
2023-07-03 6:52 ` Ze Gao
2023-07-03 6:52 ` Ze Gao
2023-05-17 3:45 ` [PATCH v3 3/4] fprobe: add recursion detection in fprobe_exit_handler Ze Gao
2023-05-17 3:45 ` Ze Gao
2023-05-17 3:45 ` [PATCH v3 4/4] rethook, fprobe: do not trace rethook related functions Ze Gao
2023-05-17 3:45 ` Ze Gao
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=20230517034510.15639-1-zegao@tencent.com \
--to=zegao2021@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=conor@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yhs@fb.com \
--cc=zegao@tencent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.