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.
Description of problem:
There is a RHEL6.1 kABI breakage on SGI UV. Some idiot (me) pushed a patch to the community that added a field to uv_hub_info_s. The community does not care about maintaining a stable ABI so the change was accepted. Since RHEL does care about maintaining kABI this is a problem. The impact is that modules built against the RHEL6.0 kernel that use the uv_hub_info structure will not load on the RHEL6.1 kernel.
This breakage was uncovered when trying to install modules built against RHEL6 onto a RHEL6.1-alpha system. Before receiving the RHEL6.1-alpha testing was done with an internally build kernel & modules so the modules & kernel matched.
The upstream patch that caused the problem is http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiffh=c8f730b1ab825f06733e1c074264f0078721f365 .
Version-Release number of selected component (if applicable):
How reproducible:
100%.
Steps to Reproduce:
1. Boot the RHEL6.1-alpha kernel.
2. Try to load a module built on RHEL6.0 that uses the uv_hub_info structure.
Actual results:
The module will not load.
Expected results:
The module should load.
Additional info:
Attached is a patch to fix the problem.
What is the status of this patch? Last I heard George posted the patch on
the RH kernel list and answered a question by Don Z. Is this patch in?
Thanks.
And in addition to that, Russ, this BZ needs acks. George knows the process.
Comment 6RHEL Program Management
2011-03-25 18:19:38 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Well it did :)
I will ping developers.
The following is is in response to Don's question on rh-kernel.
======
Hi Don,
SGI has several kernel modules that are loaded on top of the RHEL
kernels which exploit features of our NUMA hardware. The KABI
issue in question is SGI specific code which these modules rely
on. Our concern is that when customers upgrade to 6.1 the
old modules work.
In the interest of full disclosure UV2 may cause us to have to
break KABI for 6.2, the point is under discussion inside SGI.
But it would be best if we don't have force an upgrade for 6.1
on UV1. For one thing, it saves the kernel team work and
for another it makes calls to RedHat support for SGI problems
less likely :).
Cheers,
George
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0542.html