From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: yashvardhan kukreti <yashvardhankukreti@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] https://lists.lttng.org/pipermail/lttng-dev/2020-May/029631.html
Date: Mon, 27 Mar 2023 08:27:01 -0400 [thread overview]
Message-ID: <3056c476-0e3a-8cde-39e4-907602d26d76@efficios.com> (raw)
In-Reply-To: <CALx39arqYKMj_M1q_XDBfCSrSruJ5obUuNHeN4Cu7a1sVDwwbw@mail.gmail.com>
On 2023-03-26 11:00, yashvardhan kukreti wrote:
>
> Hi Mathew,
>
> I have a question about this patch for lttng-modules and the use of
> register_kprobe() to fetch the function ptr.
> The question in this regard is especially from PPC64 ELF_ABI_v1
> perspective.
>
> The functions on PPC64 are accessed via the Function descriptor
> while what register_kprobes returns is the entry point of the function.
> Hence using the return pointer tends to interpret the addr as the
> address of the function descriptor and dereferences the ppc_inst as
> the function entry point and crashes
>
> [ 4145.483594] kernel tried to execute exec-protected page
> (7c0802a6fb81ffe0) - exploit attempt? (uid: 0)
> here 7c0802a6 is the mfspr instruction from the code text section of
> the kallsyms_lookup_name()
>
> note for PPC_ELF_ABI_v1 the register_kprobes() searches for the dot
> variant of the symbol and only in case if cannot find the dot
> variant looks for the normal symbol.
> register_kprobe() -> kprobe_addr() -> kprobe_lookup_name() [arch
> variant replaces weak symbol]
> https://elixir.bootlin.com/linux/v5.10.174/C/ident/kprobe_lookup_name <https://elixir.bootlin.com/linux/v5.10.174/C/ident/kprobe_lookup_name>
>
> Please let me know if i make sense or that i may have missed something.
>
> I have looked at the code of 2.12.8 as well and 2.12.3 verstion of
> lttng-modules.
Please have a look at commits (from stable-2.12 branch of lttng-modules):
commit 53772db24facd84f1f3ddcf21a1ef5f162608721
Author: He Zhe <zhe.he@windriver.com>
Date: Tue Sep 27 15:59:42 2022 +0800
wrapper: powerpc64: fix kernel crash caused by do_get_kallsyms
commit 8fe888d86ccad4226b05a536efb73d71bb091062
Author: Michael Jeanson <mjeanson@efficios.com>
Date: Thu Nov 24 14:25:33 2022 -0500
fix: kallsyms wrapper on ppc64el
I suspect you'll also need this change currently in review:
https://review.lttng.org/c/lttng-modules/+/9113
Please let us know if especially this last change fixes things on your side.
Thanks,
Mathieu
>
> Regards,
> Shashank
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2023-03-27 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALx39aqN_YvfcDhhKgURZZU-bWZvuiZptbb-kJDYerEex9Q-7A@mail.gmail.com>
2023-03-26 15:00 ` yashvardhan kukreti via lttng-dev
2023-03-27 12:27 ` Mathieu Desnoyers via lttng-dev [this message]
2023-03-27 15:52 ` yashvardhan kukreti via lttng-dev
2023-03-27 18:29 ` Michael Jeanson via lttng-dev
2023-03-28 13:34 ` yashvardhan kukreti via lttng-dev
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=3056c476-0e3a-8cde-39e4-907602d26d76@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=yashvardhankukreti@gmail.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