From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: David Carlier <devnexen@gmail.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
martin@kaiser.cx, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] fprobe: Terminate the fgraph_data list when the reservation is not filled
Date: Fri, 18 Sep 2026 09:00:38 +0900 [thread overview]
Message-ID: <20260918090038.8bb79d5b132ea82846a4c9c5@kernel.org> (raw)
In-Reply-To: <20260917212407.384468-1-devnexen@gmail.com>
On Thu, 17 Sep 2026 22:24:07 +0100
David Carlier <devnexen@gmail.com> wrote:
> fprobe_fgraph_entry() reserves shadow stack space for every fprobe with
> an exit handler, but only fills it for those whose entry handler returns
> 0. fgraph_reserve_data() does not clear the area, so fprobe_return()
> parses the unused tail as headers left over from an earlier call, and an
> exit handler can run twice or despite its entry handler asking to skip
> it.
>
> Write a zero word after the last entry to terminate the walk. A zeroed
> slot does not decode to a NULL fprobe on the arches that encode the
> header into one unsigned long, since arch_decode_fprobe_header_fp() ORs
> in FPROBE_HEADER_MSB_PATTERN, so make read_fprobe_header() return NULL
> for a zeroed slot.
>
This fix looks good to me. Let me pick this.
Thanks!
> Fixes: e0a384434ae1 ("tracing: fprobe: do not zero out unused fgraph_data")
> Cc: stable@vger.kernel.org
> Suggested-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> Signed-off-by: David Carlier <devnexen@gmail.com>
> ---
> kernel/trace/fprobe.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/kernel/trace/fprobe.c b/kernel/trace/fprobe.c
> index 1e9b00997ff2..9f2d98181779 100644
> --- a/kernel/trace/fprobe.c
> +++ b/kernel/trace/fprobe.c
> @@ -171,6 +171,11 @@ static inline bool write_fprobe_header(unsigned long *stack,
> static inline void read_fprobe_header(unsigned long *stack,
> struct fprobe **fp, unsigned int *size_words)
> {
> + if (!*stack) {
> + *fp = NULL;
> + *size_words = 0;
> + return;
> + }
> *fp = arch_decode_fprobe_header_fp(*stack);
> *size_words = arch_decode_fprobe_header_size(*stack);
> }
> @@ -203,6 +208,12 @@ static inline void read_fprobe_header(unsigned long *stack,
> {
> struct __fprobe_header *fph = (struct __fprobe_header *)stack;
>
> + if (!*stack) {
> + *fp = NULL;
> + *size_words = 0;
> + return;
> + }
> +
> *fp = fph->fp;
> *size_words = fph->size_words;
> }
> @@ -635,6 +646,10 @@ static int fprobe_fgraph_entry(struct ftrace_graph_ent *trace, struct fgraph_ops
> }
> }
>
> + /* Terminate the list, fgraph_reserve_data() does not clear it. */
> + if (used && used < reserved_words)
> + fgraph_data[used] = 0;
> +
> /* If any exit_handler is set, data must be used. */
> return used != 0;
> }
> --
> 2.55.0
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-09-18 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 21:24 David Carlier
2026-09-18 0:00 ` Masami Hiramatsu [this message]
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=20260918090038.8bb79d5b132ea82846a4c9c5@kernel.org \
--to=mhiramat@kernel.org \
--cc=devnexen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin@kaiser.cx \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.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®