From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Ze Gao <zegao2021@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ze Gao <zegao@tencent.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] rethook: use preempt_{disable, enable}_notrace in rethook_trampoline_handler
Date: Tue, 16 May 2023 13:25:02 +0900 [thread overview]
Message-ID: <20230516132502.c51be728bd086b8c9005ce57@kernel.org> (raw)
In-Reply-To: <a17a14abfb81cb0eea77c2ee10d7fc98d5d5a73e.1684120990.git.zegao@tencent.com>
Hi Ze Gao,
Thanks for the patch.
On Mon, 15 May 2023 11:26:38 +0800
Ze Gao <zegao2021@gmail.com> wrote:
> This patch replace preempt_{disable, enable} with its corresponding
> notrace version in rethook_trampoline_handler so no worries about stack
> recursion or overflow introduced by preempt_count_{add, sub} under
> fprobe + rethook context.
So, have you ever see that recursion of preempt_count overflow case?
I intended to use the normal preempt_disable() here because it does NOT
prohibit any function-trace call (Note that both kprobes and
fprobe checks recursive call by itself) but it is used for preempt_onoff
tracer.
Thanks,
>
> Signed-off-by: Ze Gao <zegao@tencent.com>
> ---
> kernel/trace/rethook.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/rethook.c b/kernel/trace/rethook.c
> index 32c3dfdb4d6a..60f6cb2b486b 100644
> --- a/kernel/trace/rethook.c
> +++ b/kernel/trace/rethook.c
> @@ -288,7 +288,7 @@ unsigned long rethook_trampoline_handler(struct pt_regs *regs,
> * These loops must be protected from rethook_free_rcu() because those
> * are accessing 'rhn->rethook'.
> */
> - preempt_disable();
> + preempt_disable_notrace();
>
> /*
> * Run the handler on the shadow stack. Do not unlink the list here because
> @@ -321,7 +321,7 @@ unsigned long rethook_trampoline_handler(struct pt_regs *regs,
> first = first->next;
> rethook_recycle(rhn);
> }
> - preempt_enable();
> + preempt_enable_notrace();
>
> return correct_ret_addr;
> }
> --
> 2.40.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-05-16 4:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 3:52 [PATCH 0/4] Make fpobe + rethook immune to recursion Ze Gao
2023-05-15 3:26 ` [PATCH 1/4] rethook: use preempt_{disable, enable}_notrace in rethook_trampoline_handler Ze Gao
2023-05-16 4:25 ` Masami Hiramatsu [this message]
2023-05-16 5:33 ` Masami Hiramatsu
2023-05-15 3:26 ` [PATCH 2/4] fprobe: make fprobe_kprobe_handler recursion free Ze Gao
2023-05-16 1:25 ` Steven Rostedt
2023-05-16 3:02 ` Ze Gao
2023-05-15 3:26 ` [PATCH 3/4] fprobe: add recursion detection in fprobe_exit_handler Ze Gao
2023-05-16 4:25 ` Masami Hiramatsu
2023-05-15 3:26 ` [PATCH 4/4] rehook, fprobe: mark rethook related functions notrace Ze Gao
2023-05-16 4:28 ` Masami Hiramatsu
2023-05-16 7:26 ` Ze Gao
[not found] <20230515031314.7836-1-zegao@tencent.com>
2023-05-15 3:13 ` [PATCH 1/4] rethook: use preempt_{disable, enable}_notrace in rethook_trampoline_handler 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=20230516132502.c51be728bd086b8c9005ce57@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=zegao2021@gmail.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 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).