From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Alexey Gladkov <legion@kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v5 03/10] kbuild: keep .modinfo section in vmlinux.unstripped
Date: Mon, 28 Jul 2025 15:57:53 +0200 [thread overview]
Message-ID: <20250728135753.432695A72-agordeev@linux.ibm.com> (raw)
In-Reply-To: <d44055fc22d4a53b7f87758d31cb4d640c8f8cca.1753354215.git.legion@kernel.org>
On Thu, Jul 24, 2025 at 03:49:40PM +0200, Alexey Gladkov wrote:
Hi Alexey, Masahiro,
> From: Masahiro Yamada <masahiroy@kernel.org>
>
> Keep the .modinfo section during linking, but strip it from the final
> vmlinux.
>
> Adjust scripts/mksysmap to exclude modinfo symbols from kallsyms.
>
> This change will allow the next commit to extract the .modinfo section
> from the vmlinux.unstripped intermediate.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> include/asm-generic/vmlinux.lds.h | 2 +-
> scripts/Makefile.vmlinux | 2 +-
> scripts/mksysmap | 3 +++
> 3 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> index fa5f19b8d53a..1791665006f9 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -831,6 +831,7 @@ defined(CONFIG_AUTOFDO_CLANG) || defined(CONFIG_PROPELLER_CLANG)
>
> /* Required sections not related to debugging. */
> #define ELF_DETAILS \
> + .modinfo : { *(.modinfo) } \
FWIW, to me .modinfo logically does not quite belong to ELF_DETAILS,
since it is not about ELF.
I would guess, that you want to make a minimal code impact to the
linker scripts, but with that you turn .modinfo the only section
among ones that do not make it to the final image:
STABS_DEBUG
DWARF_DEBUG
ELF_DETAILS
That immediately breaks s390, but also is a call for trouble in
the future, as far as I am concerned.
Would it makes sense to introduce e.g MODINFO instead?
> .comment 0 : { *(.comment) } \
> .symtab 0 : { *(.symtab) } \
> .strtab 0 : { *(.strtab) } \
> @@ -1044,7 +1045,6 @@ defined(CONFIG_AUTOFDO_CLANG) || defined(CONFIG_PROPELLER_CLANG)
> *(.discard.*) \
> *(.export_symbol) \
> *(.no_trim_symbol) \
> - *(.modinfo) \
> /* ld.bfd warns about .gnu.version* even when not emitted */ \
> *(.gnu.version*) \
Thanks!
next prev parent reply other threads:[~2025-07-28 13:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 13:49 [PATCH v5 00/10] Add generated modalias to modules.builtin.modinfo Alexey Gladkov
2025-07-24 13:49 ` [PATCH v5 01/10] module: remove meaningless 'name' parameter from __MODULE_INFO() Alexey Gladkov
2025-07-24 13:49 ` [PATCH v5 02/10] kbuild: always create intermediate vmlinux.unstripped Alexey Gladkov
2025-07-24 13:49 ` [PATCH v5 03/10] kbuild: keep .modinfo section in vmlinux.unstripped Alexey Gladkov
2025-07-28 13:57 ` Alexander Gordeev [this message]
2025-07-28 15:15 ` Alexey Gladkov
2025-07-29 13:54 ` Masahiro Yamada
2025-07-24 13:49 ` [PATCH v5 04/10] kbuild: extract modules.builtin.modinfo from vmlinux.unstripped Alexey Gladkov
2025-07-24 13:49 ` [PATCH v5 05/10] scsi: Always define blogic_pci_tbl structure Alexey Gladkov
2025-07-24 13:49 ` [PATCH v5 06/10] pinctrl: meson: Fix typo in device table macro Alexey Gladkov
2025-07-24 14:09 ` Neil Armstrong
2025-07-24 13:49 ` [PATCH v5 07/10] modpost: Add modname to mod_device_table alias Alexey Gladkov
2025-07-24 16:00 ` Miguel Ojeda
2025-07-24 13:49 ` [PATCH v5 08/10] modpost: Create modalias for builtin modules Alexey Gladkov
2025-07-24 13:49 ` [PATCH v5 09/10] kbuild: vmlinux.unstripped should always depend on .vmlinux.export.o Alexey Gladkov
2025-07-24 13:49 ` [PATCH v5 10/10] s390: vmlinux.lds.S: Reorder sections Alexey Gladkov
2025-07-26 10:59 ` Masahiro Yamada
2025-07-28 14:01 ` Heiko Carstens
2025-07-28 15:18 ` Alexey Gladkov
2025-07-29 12:46 ` Masahiro Yamada
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=20250728135753.432695A72-agordeev@linux.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=da.gomez@samsung.com \
--cc=legion@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.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