Meaning
Source code visibility macros inside operating system kernels mark specific internal functions as accessible strictly to loadable modules that declare compatible open-source licensing. Kernel authors apply export_symbol_gpl within the core infrastructure to protect subsystems like network stacks, direct memory operations, and memory managers from proprietary wrapper exploitation. The mechanism stops dynamic linking during module initialization if the binary payload does not provide an explicit free software declaration.
Its governance ceases at the user-space boundary, exercising control only over kernel execution threads.
Linkage Enforcement
Kernel loaders parse module metadata at insertion time, comparing declared licenses against exposed symbol tables. When an out-of-tree binary claims non-compliant licensing while resolving symbols governed by export_symbol_gpl, the operating system aborts symbol resolution and drops module initialization with permission faults. The symbol loader marks the running kernel as tainted if forced symbol overrides are detected during boot cycles.
This strict barrier prevents vendors from hiding custom protocol engines behind thin compliance layers. System logs explicitly trace linkage rejections, identifying the precise symbol offset that halted execution.
Vendor Adaptation
Hardware module suppliers face architectural limitations when bridging proprietary wireless modem firmware across open platforms. Some vendors introduce intermediate open-source glue layers designed to consume export_symbol_gpl entry points while forwarding control signals to closed-source binary blobs. Upstream maintainers classify this practice as license evasion, creating engineering debt during platform transitions.
Board bring-up requires verifying whether third-party wireless drivers depend on restricted symbol sets.
Legal Verification
Supply chain compliance requires automated scanning of compiled binary modules before factory image flashing. Release teams execute script-based checks over symbol tables to ensure proprietary connectivity drivers avoid unpermitted kernel exports. An external compliance audit sheet documents module license strings against upstream table baselines.
Validation passes when clean symbols populate the integration build log.