From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Lei wang <quic_leiwan@quicinc.com>, lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] [PATCH lttng-modules] Android: Import VFS namespace for android common kernel
Date: Mon, 18 Dec 2023 11:31:07 -0500 [thread overview]
Message-ID: <adc94b8a-b711-4da4-b90d-fd07fccddb58@efficios.com> (raw)
In-Reply-To: <20231218101633.4188511-1-quic_leiwan@quicinc.com>
On 2023-12-18 05:16, Lei wang via lttng-dev wrote:
> Android GKI kernel add limitation on fs interface usage.
> Need to import VFS namespace explicitly to make it workable
> for lttng-modules.
>
Merged into lttng-modules master and 2.13 branches, thanks!
Mathieu
> Signed-off-by: Lei wang <quic_leiwan@quicinc.com>
> ---
> src/wrapper/kallsyms.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/src/wrapper/kallsyms.c b/src/wrapper/kallsyms.c
> index 97897c4..9398c83 100644
> --- a/src/wrapper/kallsyms.c
> +++ b/src/wrapper/kallsyms.c
> @@ -113,3 +113,7 @@ unsigned long wrapper_kallsyms_lookup_name(const char *name)
> EXPORT_SYMBOL_GPL(wrapper_kallsyms_lookup_name);
>
> #endif
> +
> +#ifdef CONFIG_ANDROID
> +MODULE_IMPORT_NS(VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver);
> +#endif
--
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
prev parent reply other threads:[~2023-12-18 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 10:16 [lttng-dev] [PATCH lttng-modules] Android: Import VFS namespace for android common kernel Lei wang via lttng-dev
2023-12-18 16:31 ` Mathieu Desnoyers via lttng-dev [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=adc94b8a-b711-4da4-b90d-fd07fccddb58@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=quic_leiwan@quicinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).