From: jpoimboe@redhat.com (Josh Poimboeuf)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm64: reliable stacktraces
Date: Fri, 10 Aug 2018 15:44:49 -0500 [thread overview]
Message-ID: <20180810204449.4asgonydn6yfb6kq@treble> (raw)
In-Reply-To: <20180810160311.C988D68CF4@newverein.lst.de>
On Fri, Aug 10, 2018 at 06:03:11PM +0200, Torsten Duwe wrote:
> This is more an RFC in the original sense: is this basically
> the correct approach? (as I had to tweak the API a bit).
>
> In particular the code does not detect interrupts and exception
> frames, and does not yet check whether the code address is valid.
> The latter check would also have to be omitted for the latest frame
> on other tasks' stacks. This would require some more tweaking.
>
> unwind_frame() now reports whether we had to stop normally or due to
> an error condition; walk_stackframe() will pass that info.
> __save_stack_trace() is used for a start to check the validity of a
> frame; maybe save_stack_trace_tsk_reliable() will need its own callback.
>
> Any comments welcome.
>
> Signed-off-by: Torsten Duwe <duwe@suse.de>
Before we do this we'll need the same analysis we did for ppc64le to
figure out if objtool is needed.
--
Josh
prev parent reply other threads:[~2018-08-10 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 16:00 [PATCH 0/3] arm64 live patching Torsten Duwe
2018-08-10 16:02 ` [PATCH 1/3] arm64: implement ftrace with regs Torsten Duwe
2018-08-10 19:27 ` Steven Rostedt
2018-08-13 10:54 ` Julien Thierry
2018-08-14 2:03 ` Steven Rostedt
2018-08-14 8:33 ` Julien Thierry
2018-08-14 16:04 ` Steven Rostedt
2018-08-15 13:47 ` Torsten Duwe
2018-08-10 16:03 ` [PATCH 2/3] arm64: implement live patching Torsten Duwe
2018-08-29 11:37 ` Miroslav Benes
2018-08-10 16:03 ` [PATCH 3/3] arm64: reliable stacktraces Torsten Duwe
2018-08-10 20:44 ` Josh Poimboeuf [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=20180810204449.4asgonydn6yfb6kq@treble \
--to=jpoimboe@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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