public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, broonie@kernel.org,
	catalin.marinas@arm.com, kaleshsingh@google.com,
	madvenka@linux.microsoft.com
Subject: Re: [PATCH 1/3] arm64: stacktrace: recover return address for first entry
Date: Thu, 6 Apr 2023 16:25:50 +0100	[thread overview]
Message-ID: <20230406152549.GA11908@willie-the-truck> (raw)
In-Reply-To: <20230324134958.2496891-2-mark.rutland@arm.com>

On Fri, Mar 24, 2023 at 01:49:56PM +0000, Mark Rutland wrote:
> The function which calls the top-level backtracing function may have
> been instrumented with ftrace and/or kprobes, and hence the first return
> address may have been rewritten.
> 
> Factor out the existing fgraph / kretprobes address recovery, and use
> this for the first address. As the comment for the fgraph case isn't all
> that helpful, I've also dropped that.
> 
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Kalesh Singh <kaleshsingh@google.com>
> Cc: Madhavan T. Venkataraman <madvenka@linux.microsoft.com>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Will Deacon <will@kernel.org>
> ---
>  arch/arm64/kernel/stacktrace.c | 52 +++++++++++++++++++---------------
>  1 file changed, 29 insertions(+), 23 deletions(-)
> 
> diff --git a/arch/arm64/kernel/stacktrace.c b/arch/arm64/kernel/stacktrace.c
> index 83154303e682c..219ce0668a3dd 100644
> --- a/arch/arm64/kernel/stacktrace.c
> +++ b/arch/arm64/kernel/stacktrace.c
> @@ -69,6 +69,31 @@ static __always_inline void unwind_init_from_task(struct unwind_state *state,
>  	state->pc = thread_saved_pc(task);
>  }
>  
> +static __always_inline int
> +unwind_recover_return_address(struct unwind_state *state)
> +{
> +	struct task_struct *tsk = state->task;
> +
> +#ifdef CONFIG_FUNCTION_GRAPH_TRACER
> +	if (tsk->ret_stack &&
> +	    (state->pc == (unsigned long)return_to_handler)) {
> +		unsigned long orig_pc;
> +		orig_pc = ftrace_graph_ret_addr(tsk, NULL, state->pc,
> +						(void *)state->fp);
> +		if (WARN_ON_ONCE(state->pc == orig_pc))
> +			return -EINVAL;
> +		state->pc = orig_pc;
> +	}
> +#endif /* CONFIG_FUNCTION_GRAPH_TRACER */
> +
> +#ifdef CONFIG_KRETPROBES
> +	if (is_kretprobe_trampoline(state->pc))
> +		state->pc = kretprobe_find_ret_addr(tsk, (void *)state->fp, &state->kr_cur);
> +#endif /* CONFIG_KRETPROBES */
> +
> +	return 0;
> +}

This generates an unused variable warning with defconfig:

arch/arm64/kernel/stacktrace.c: In function ‘unwind_recover_return_address’:
arch/arm64/kernel/stacktrace.c:78:22: warning: unused variable ‘tsk’ [-Wunused-variable]
   78 |  struct task_struct *tsk = state->task;
      |                      ^~~
 

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-04-06 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 13:49 [PATCH 0/3] arm64: stacktrace: cleanups Mark Rutland
2023-03-24 13:49 ` [PATCH 1/3] arm64: stacktrace: recover return address for first entry Mark Rutland
2023-03-29  8:58   ` Kalesh Singh
2023-04-06 15:25   ` Will Deacon [this message]
2023-04-11 16:12     ` Mark Rutland
2023-03-24 13:49 ` [PATCH 2/3] arm64: stacktrace: move dump functions to end of file Mark Rutland
2023-03-29  8:58   ` Kalesh Singh
2023-03-24 13:49 ` [PATCH 3/3] arm64: stacktrace: always inline core stacktrace functions Mark Rutland
2023-03-29  8:59   ` Kalesh Singh

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=20230406152549.GA11908@willie-the-truck \
    --to=will@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=madvenka@linux.microsoft.com \
    --cc=mark.rutland@arm.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