From: Juergen Gross <jgross@suse.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
moderated for non-subscribers <xen-devel@lists.xenproject.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Julien Grall <julien.grall@arm.com>,
Shannon Zhao <shannon.zhao@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen: unexport __init-annotated xen_xlate_map_ballooned_pages()
Date: Wed, 8 Jun 2022 07:37:09 +0200 [thread overview]
Message-ID: <d7ab14e9-2411-774e-21f1-2ecf3cffd2e9@suse.com> (raw)
In-Reply-To: <20220606045920.4161881-1-masahiroy@kernel.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 980 bytes --]
On 06.06.22 06:59, Masahiro Yamada wrote:
> EXPORT_SYMBOL and __init is a bad combination because the .init.text
> section is freed up after the initialization. Hence, modules cannot
> use symbols annotated __init. The access to a freed symbol may end up
> with kernel panic.
>
> modpost used to detect it, but it has been broken for a decade.
>
> Recently, I fixed modpost so it started to warn it again, then this
> showed up in linux-next builds.
>
> There are two ways to fix it:
>
> - Remove __init
> - Remove EXPORT_SYMBOL
>
> I chose the latter for this case because none of the in-tree call-sites
> (arch/arm/xen/enlighten.c, arch/x86/xen/grant-table.c) is compiled as
> modular.
>
> Fixes: 243848fc018c ("xen/grant-table: Move xlated_setup_gnttab_pages to common place")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Pushed to xen/tip.git for-linus-5.19a
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2022-06-08 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 4:59 Masahiro Yamada
2022-06-06 16:17 ` Oleksandr
2022-06-06 23:43 ` Stefano Stabellini
2022-06-08 5:37 ` Juergen Gross [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=d7ab14e9-2411-774e-21f1-2ecf3cffd2e9@suse.com \
--to=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sfr@canb.auug.org.au \
--cc=shannon.zhao@linaro.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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®