Third-party kernel modules subtest

The third-party kernel subtest checks whether non-Red Hat kernel packages are running.

The use of partner kernel modules has the potential to introduce risks to the Red Hat kernel that may not be fully ascertained during certification. As a result, when partner kernel modules are required, the certification process aims to ensure that the stack remains supportable, and the partner’s responsibilities are clearly delineated.

Red Hat reserves the right to deny a certification whenever partner kernel modules are required. Partner kernel modules are subject to additional verification, including (but not limited to) the following:

Success criteria
  • Partners must:
    • Agree that you understand and will act according to the policies defined in Red Hat’s production scope of coverage.
    • Agree that you understand and will act according to the policies defined in Red Hat’s third party support policy.
    • Provide Red Hat the documentation of kernel modules written for joint customers.
    • Provide Red Hat the contact information of your application support team and kernel engineering support team
    • Declare that you own and support the module.
    • Declare that module will not interfere with the RHEL kernel or userland functionality.
    • Declare that module is not a hardware driver.
  • Partner kernel modules must:
    • Show the module name, size, and dependencies in the output of the lsmod command.
    • Show the module name, filename, license, and description in the output of the modinfo command, aligned with the partner documentation.
    • Show that the partner signs and supports the module in the output of the modinfo command.
    • Be precompiled ko or ko.xz kmods.
    • Be loaded after the final pivot_root.
    • Be delivered and packaged in an RPM or other format that is signed by the partner. It must also provide a mechanism to validate both the in-memory and on-disk kernel module.
  • If delivered and packaged as an RPM, partner kernel modules must:
    • Meet the standard RHEL RPM certification requirements.
    • Show that the package’s vendor is responsible for its support in the output of the rpm -qi command.
    • Show the supported Red Hat kernel range for the kernel modules in the output of the rpm -q --requires command.