Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hi,
I understand the situation is not optimal for users, but I'm really not in
favor of the alternative which is to constantly adjust userspace package
documentation to changing kernel features.
Whenever I rebase a package I would have to check every bit of docs and remove
anything that's not supported by the kernel. Keeping userspace in sync with
kernel is already error-prone, often RFEs are filed against kernel and only
last minute for userspace (which is mandatory if a customer is supposed to use
the feature). Absolutely nobody expects userspace docs to need changes if a new
kernel feature is already supported by the code itself.
If you consider this a significant problem we should solve, please reopen and
escalate this ticket. Because if we are to solve it, we need management in the
boat and I need help with it to still get "normal" bugs fixed.
Cheers, Phil