From: Siddharth Nayyar <sidnayyar@google.com>
To: petr.pavlu@suse.com, corbet@lwn.net
Cc: arnd@arndb.de, linux-arch@vger.kernel.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org, mcgrof@kernel.org,
nathan@kernel.org, nicolas.schier@linux.dev,
samitolvanen@google.com, sidnayyar@google.com,
maennich@google.com, gprocida@google.com
Subject: [PATCH v3 0/8] scalable symbol flags with __kflagstab
Date: Mon, 3 Nov 2025 16:19:46 +0000 [thread overview]
Message-ID: <20251103161954.1351784-1-sidnayyar@google.com> (raw)
This patch series implements a mechanism for scalable exported symbol
flags using a separate section called __kflagstab. The series introduces
__kflagstab support, removes *_gpl sections in favor of a GPL flag,
simplifies symbol resolution during module loading.
This series previously added symbol import protection which aims to
restrict the use of "protected symbol" exported by vmlinux, as a use
case for which __kflagstab is being introduced. Such symbols are only
allowed to be imported by signed modules when symbol protection is
enabled. This functionality requires more thought and discussion [1],
and therefore I will create a separate patch series for it. In the
meantime, this series now only focuses on introduction of __kflagstab
which right is an improvement to the module loader's code health [2].
Thank you Petr Pavlu and Jonathan Corbet for their valuable feedback.
---
Changes from v2:
- removed symbol import protection to spin off into its own series
v2:
https://lore.kernel.org/20251013153918.2206045-1-sidnayyar@google.com/
Changes from v1:
- added a check to ensure __kflagstab is present
- added warnings for the obsolete *_gpl sections
- moved protected symbol check before ref_module() call
- moved protected symbol check failure warning to issue detection point
v1:
https://lore.kernel.org/20250829105418.3053274-1-sidnayyar@google.com/
[1] https://lore.kernel.org/cac5ed5e-3320-4db0-99d8-ea5e97e56bfb@suse.com/
[2] https://lore.kernel.org/2bf54830-ea9c-4962-a7ef-653fbed8f8c0@suse.com/
Siddharth Nayyar (8):
define kernel symbol flags
linker: add kflagstab section to vmlinux and modules
modpost: create entries for kflagstab
module loader: use kflagstab instead of *_gpl sections
modpost: put all exported symbols in ksymtab section
module loader: remove references of *_gpl sections
linker: remove *_gpl sections from vmlinux and modules
remove references to *_gpl sections in documentation
Documentation/kbuild/modules.rst | 11 ++--
include/asm-generic/vmlinux.lds.h | 21 ++----
include/linux/export-internal.h | 28 +++++---
include/linux/module.h | 4 +-
include/linux/module_symbol.h | 5 ++
kernel/module/internal.h | 4 +-
kernel/module/main.c | 102 ++++++++++++++----------------
scripts/mod/modpost.c | 16 +++--
scripts/module.lds.S | 3 +-
9 files changed, 99 insertions(+), 95 deletions(-)
--
2.51.1.930.gacf6e81ea2-goog
next reply other threads:[~2025-11-03 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 16:19 Siddharth Nayyar [this message]
2025-11-03 16:19 ` [PATCH v3 1/8] define kernel symbol flags Siddharth Nayyar
2025-11-03 16:19 ` [PATCH v3 2/8] linker: add kflagstab section to vmlinux and modules Siddharth Nayyar
2025-11-03 16:19 ` [PATCH v3 3/8] modpost: create entries for kflagstab Siddharth Nayyar
2025-11-03 16:19 ` [PATCH v3 4/8] module loader: use kflagstab instead of *_gpl sections Siddharth Nayyar
2025-11-03 16:19 ` [PATCH v3 5/8] modpost: put all exported symbols in ksymtab section Siddharth Nayyar
2025-11-03 16:19 ` [PATCH v3 6/8] module loader: remove references of *_gpl sections Siddharth Nayyar
2025-11-03 16:19 ` [PATCH v3 7/8] linker: remove *_gpl sections from vmlinux and modules Siddharth Nayyar
2025-11-03 16:19 ` [PATCH v3 8/8] remove references to *_gpl sections in documentation Siddharth Nayyar
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=20251103161954.1351784-1-sidnayyar@google.com \
--to=sidnayyar@google.com \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=gprocida@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=maennich@google.com \
--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
all inboxes | Powered by JetHome®