Cloud Platform

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Categories ClearCase
Created by Guest
Created on Apr 1, 2020

MVFS Taints Kernel on RHEL 7

We receive a message in the Linux messages file: "kernel: mvfs: module verification failed: signature and/or required key missing - tainting kernel" for our Linux 7 systems.

This is expected since Red Hat Enterprise Linux messages concerning tainted kernels have changed in RHEL 7. In RHEL 7 any loaded driver module that is built outside of a full Linux kernel build will taint the kernel. In RHEL 7 any kernel module that cannot be authenticated with a public key from the kernel's system key ring will taint the kernel. This could be either because the module was not signed or the required public key could not be found.
See: https://access.redhat.com/solutions/800133

Use Case
This will occur with all Linux 7 users. However, it is possible to compile the kernel to not load the module if it is not signed with higher security systems. The kernel can be configured to * not * issue a warning if the kernel is signed, even if the public key is not loaded in the kernel. If the boot is UEFI with signed modules, the unsigned module will not load.
RFE ID 141402
RFE URL
RFE Product Rational ClearCase
Idea Priority Medium