From: Steven Rostedt <rostedt@goodmis.org>
To: Li Bin <huawei.libin@huawei.com>
Cc: <mingo@redhat.com>, <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, <x86@kernel.org>
Subject: Re: [PATCH v2 5/5] x86: ftrace: fix the comments for ftrace_modify_code_direct
Date: Wed, 23 Dec 2015 12:37:25 -0500 [thread overview]
Message-ID: <20151223123725.1923be18@gandalf.local.home> (raw)
In-Reply-To: <1449367378-29430-6-git-send-email-huawei.libin@huawei.com>
On Sun, 6 Dec 2015 10:02:58 +0800
Li Bin <huawei.libin@huawei.com> wrote:
> There is no need to worry about module and __init text disappearing
> case, because that ftrace has a module notifier that is called when
> a module is being unloaded and before the text goes away and this
> code grabs the ftrace_lock mutex and removes the module functions
> from the ftrace list, such that it will no longer do any
> modifications to that module's text, the update to make functions
> be traced or not is done under the ftrace_lock mutex as well.
> And by now, __init section codes should not been modified
> by ftrace, because it is black listed in recordmcount.c and
> ignored by ftrace.
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Suggested-by: Steven Rostedt <rostedt@goodmis.org>
> Signed-off-by: Li Bin <huawei.libin@huawei.com>
> ---
> arch/x86/kernel/ftrace.c | 12 +++++-------
> 1 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/kernel/ftrace.c b/arch/x86/kernel/ftrace.c
> index 311bcf3..db0f6b1 100644
> --- a/arch/x86/kernel/ftrace.c
> +++ b/arch/x86/kernel/ftrace.c
> @@ -106,13 +106,11 @@ ftrace_modify_code_direct(unsigned long ip, unsigned const char *old_code,
> unsigned char replaced[MCOUNT_INSN_SIZE];
>
> /*
> - * Note: Due to modules and __init, code can
> - * disappear and change, we need to protect against faulting
> - * as well as code changing. We do this by using the
> - * probe_kernel_* functions.
> - *
> - * No real locking needed, this code is run through
> - * kstop_machine, or before SMP starts.
> + * Note:
> + * We are paranoid about modifying text, as if a bug was to happen, it
> + * could cause us to read or write to someplace that could cause harm.
> + * Carefully read and modify the code with probe_kernel_*(), and make
> + * sure what we read is what we expected it to be before modifying it.
> */
Thomas,
This has been now fixed. You want to ack it and I take it, or can you
take it. Or is there something else that should be fixed?
-- Steve
>
> /* read the text we want to modify */
next prev parent reply other threads:[~2015-12-23 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 2:02 [PATCH v2 0/5] ftrace: fix ftrace misleading comments for arch using it Li Bin
2015-12-06 2:02 ` [PATCH v2 1/5] ia64: ftrace: fix the comments for ftrace_modify_code Li Bin
2015-12-06 2:02 ` [PATCH v2 2/5] metag: " Li Bin
2015-12-23 17:33 ` Steven Rostedt
2015-12-23 17:39 ` James Hogan
2015-12-06 2:02 ` [PATCH v2 3/5] powerpc: " Li Bin
2015-12-23 17:34 ` Steven Rostedt
2015-12-06 2:02 ` [PATCH v2 4/5] sh: " Li Bin
2015-12-06 2:02 ` [PATCH v2 5/5] x86: ftrace: fix the comments for ftrace_modify_code_direct Li Bin
2015-12-23 17:37 ` Steven Rostedt [this message]
2015-12-29 13:35 ` Thomas Gleixner
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=20151223123725.1923be18@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=hpa@zytor.com \
--cc=huawei.libin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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®