From: Chen Zhongjin <chenzhongjin@huawei.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
<linux@armlinux.org.uk>, <arnd@arndb.de>, <ardb@kernel.org>,
<rmk+kernel@armlinux.org.uk>, <rostedt@goodmis.org>,
<nick.hawkins@hpe.com>, <john@phrozen.org>, <mhiramat@kernel.org>
Subject: Re: [RESEND PATCH] ARM: Recover kretprobes return address for EABI stack unwinder
Date: Mon, 22 Aug 2022 22:43:09 +0800 [thread overview]
Message-ID: <a271d041-08fa-c2db-f2ac-d64d9b119797@huawei.com> (raw)
In-Reply-To: <CACRpkdZsdggUptPkPhzzu8vv9moSO+rjvZxZRb1VqJ2xWjY=HQ@mail.gmail.com>
On 2022/8/22 19:20, Linus Walleij wrote:
> On Mon, Aug 15, 2022 at 1:06 PM Chen Zhongjin <chenzhongjin@huawei.com> wrote:
>
>> 'fed240d9c974 ("ARM: Recover kretprobe modified return address in stacktrace")'
>> has implemented kretprobes return address recovery for FP
>> unwinder, this patch makes it works for EABI unwinder.
>>
>> It saves __kretprobe_trampoline address in LR on stack to identify
>> and recover the correct return address in EABI unwinder.
>>
>> Since EABI doesn't use r11 as frame pointer, we need to use SP to
>> identify different kretprobes addresses. Here the value of SP has fixed
>> distance to conventional FP position so it's fine to use it.
>>
>> Passed kunit kprobes_test on QEMU.
>>
>> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
> This looks correct to me FWIW I understand the assembly
> but I'm vaguely unfamiliar with the kprobe API, but anyway:
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Would you please drop it into Russell's patch tracker?
Done for it.
Thanks for review!
Best,
Chen
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2022-08-22 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 11:02 Chen Zhongjin
2022-08-22 11:20 ` Linus Walleij
2022-08-22 14:43 ` Chen Zhongjin [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-15 10:58 Chen Zhongjin
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=a271d041-08fa-c2db-f2ac-d64d9b119797@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=john@phrozen.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mhiramat@kernel.org \
--cc=nick.hawkins@hpe.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.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®