From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Li Huafei <lihuafei1@huawei.com>
Cc: <naveen.n.rao@linux.ibm.com>, <anil.s.keshavamurthy@intel.com>,
<rostedt@goodmis.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kprobes: Fix check for probe enabled in kill_kprobe()
Date: Mon, 28 Nov 2022 17:48:43 +0900 [thread overview]
Message-ID: <20221128174843.244d5485156daf53b6406482@kernel.org> (raw)
In-Reply-To: <20221126114316.201857-1-lihuafei1@huawei.com>
On Sat, 26 Nov 2022 19:43:16 +0800
Li Huafei <lihuafei1@huawei.com> wrote:
> In kill_kprobe(), the check whether disarm_kprobe_ftrace() needs to be
> called always fails. This is because before that we set the
> KPROBE_FLAG_GONE flag for kprobe so that "!kprobe_disabled(p)" is always
> false.
Good catch!
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you!
>
> The disarm_kprobe_ftrace() call introduced by commit:
>
> 0cb2f1372baa ("kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler")
>
> to fix the NULL pointer reference problem. When the probe is enabled, if
> we do not disarm it, this problem still exists.
>
> Fix it by putting the probe enabled check before setting the
> KPROBE_FLAG_GONE flag.
>
> Fixes: 3031313eb3d54 ("kprobes: Fix to check probe enabled before disarm_kprobe_ftrace()")
> Signed-off-by: Li Huafei <lihuafei1@huawei.com>
> ---
> kernel/kprobes.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index 3050631e528d..a35074f0daa1 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -2364,6 +2364,14 @@ static void kill_kprobe(struct kprobe *p)
>
> lockdep_assert_held(&kprobe_mutex);
>
> + /*
> + * The module is going away. We should disarm the kprobe which
> + * is using ftrace, because ftrace framework is still available at
> + * 'MODULE_STATE_GOING' notification.
> + */
> + if (kprobe_ftrace(p) && !kprobe_disabled(p) && !kprobes_all_disarmed)
> + disarm_kprobe_ftrace(p);
> +
> p->flags |= KPROBE_FLAG_GONE;
> if (kprobe_aggrprobe(p)) {
> /*
> @@ -2380,14 +2388,6 @@ static void kill_kprobe(struct kprobe *p)
> * the original probed function (which will be freed soon) any more.
> */
> arch_remove_kprobe(p);
> -
> - /*
> - * The module is going away. We should disarm the kprobe which
> - * is using ftrace, because ftrace framework is still available at
> - * 'MODULE_STATE_GOING' notification.
> - */
> - if (kprobe_ftrace(p) && !kprobe_disabled(p) && !kprobes_all_disarmed)
> - disarm_kprobe_ftrace(p);
> }
>
> /* Disable one kprobe */
> --
> 2.17.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2022-11-28 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 11:43 Li Huafei
2022-11-28 8:48 ` Masami Hiramatsu [this message]
2022-11-28 19:21 ` Steven Rostedt
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=20221128174843.244d5485156daf53b6406482@kernel.org \
--to=mhiramat@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=rostedt@goodmis.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®