From: "Madhavan T. Venkataraman" <madvenka@linux•microsoft.com>
To: Mark Brown <broonie@kernel•org>
Cc: mark.rutland@arm•com, jpoimboe@redhat•com, ardb@kernel•org,
nobuta.keiya@fujitsu•com, catalin.marinas@arm•com,
will@kernel•org, jmorris@namei•org, pasha.tatashin@soleen•com,
jthierry@redhat•com, linux-arm-kernel@lists•infradead.org,
live-patching@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: Fri, 4 Jun 2021 15:40:45 -0500 [thread overview]
Message-ID: <39a46b62-7890-e952-3d77-756a53783176@linux.microsoft.com> (raw)
In-Reply-To: <20210604165945.GA39381@sirena.org.uk>
On 6/4/21 11:59 AM, Mark Brown wrote:
> On Wed, May 26, 2021 at 04:49:17PM -0500, madvenka@linux•microsoft.com wrote:
>
>> + * - return_to_handler() is handled by the unwinder by attempting to
>> + * retrieve the original return address from the per-task return
>> + * address stack.
>> + *
>> + * - kretprobe_trampoline() can be handled in a similar fashion by
>> + * attempting to retrieve the original return address from the per-task
>> + * kretprobe instance list.
>> + *
>> + * - I reckon optprobes can be handled in a similar fashion in the future?
>
> Note that there's a patch for optprobes on the list now:
>
> https://lore.kernel.org/r/1622803839-27354-1-git-send-email-liuqi115@huawei.com
Yes. I saw that.
Madhavan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-04 20:42 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 [this message]
2021-06-16 1:52 ` Suraj Jitindar Singh
2021-06-16 9:15 ` nobuta.keiya
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=39a46b62-7890-e952-3d77-756a53783176@linux.microsoft.com \
--to=madvenka@linux$(echo .)microsoft.com \
--cc=ardb@kernel$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=jpoimboe@redhat$(echo .)com \
--cc=jthierry@redhat$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=live-patching@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=nobuta.keiya@fujitsu$(echo .)com \
--cc=pasha.tatashin@soleen$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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