From: "nobuta.keiya@fujitsu.com" <nobuta.keiya@fujitsu.com>
To: 'Suraj Jitindar Singh' <sjitindarsingh@gmail.com>,
"madvenka@linux.microsoft.com" <madvenka@linux.microsoft.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"jpoimboe@redhat.com" <jpoimboe@redhat.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"jmorris@namei.org" <jmorris@namei.org>,
"pasha.tatashin@soleen.com" <pasha.tatashin@soleen.com>,
"jthierry@redhat.com" <jthierry@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"live-patching@vger.kernel.org" <live-patching@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH v5 2/2] arm64: Create a list of SYM_CODE functions, check return PC against list
Date: Wed, 16 Jun 2021 09:15:06 +0000 [thread overview]
Message-ID: <TY2PR01MB525710706D9D48563F240052850F9@TY2PR01MB5257.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <712b44d2af8f8cd3199aad87eb3bc94ea22d6f4a.camel@gmail.com>
Hi Suraj,
>
> if (frame->fp == (unsigned long)task_pt_regs(tsk)->stackframe)
> return -ENOENT;
If I understand correctly, a similar final frame check is introduced in this patch:
arm64: Implement stack trace termination record
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?id=7d7b720a4b80
It is currently merged into for-next/stacktrace branch.
Thanks & Best Regards,
Keiya Nobuta <nobuta.keiya@fujitsu.com>
---------------------------------------------------------
Solution Development Dept. Software Div.
FUJITSU COMPUTER TECHNOLOGIES Ltd.
next prev parent reply other threads:[~2021-06-16 9:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ea0ef9ed6eb34618bcf468fbbf8bdba99e15df7d>
2021-05-26 21:49 ` [RFC PATCH v5 0/2] arm64: Implement stack trace reliability checks madvenka
2021-05-26 21:49 ` [RFC PATCH v5 1/2] arm64: Introduce stack trace reliability checks in the unwinder madvenka
2021-06-24 14:40 ` Mark Rutland
2021-06-24 16:03 ` Mark Brown
2021-06-25 15:39 ` Madhavan T. Venkataraman
2021-06-25 15:51 ` Mark Brown
2021-06-25 17:05 ` Madhavan T. Venkataraman
2021-06-25 17:18 ` Madhavan T. Venkataraman
2021-06-26 15:35 ` Madhavan T. Venkataraman
2021-06-29 16:47 ` Josh Poimboeuf
2021-05-26 21:49 ` [RFC PATCH v5 2/2] arm64: Create a list of SYM_CODE functions, check return PC against list madvenka
2021-06-04 16:24 ` Mark Brown
2021-06-04 20:38 ` Madhavan T. Venkataraman
2021-06-04 16:59 ` Mark Brown
2021-06-04 20:40 ` Madhavan T. Venkataraman
2021-06-16 1:52 ` Suraj Jitindar Singh
2021-06-16 9:15 ` nobuta.keiya [this message]
2021-06-16 11:10 ` Madhavan T. Venkataraman
2021-06-04 15:29 ` [RFC PATCH v5 0/2] arm64: Implement stack trace reliability checks Mark Brown
2021-06-04 20:44 ` Madhavan T. Venkataraman
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=TY2PR01MB525710706D9D48563F240052850F9@TY2PR01MB5257.jpnprd01.prod.outlook.com \
--to=nobuta.keiya@fujitsu.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jmorris@namei.org \
--cc=jpoimboe@redhat.com \
--cc=jthierry@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=mark.rutland@arm.com \
--cc=pasha.tatashin@soleen.com \
--cc=sjitindarsingh@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).