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.
The receive functions {napi,vlan}_gro_{frags,receive} in the RHEL kernel return NET_RX_* results. Most drivers do not care about the return value, but sfc would like to know the GRO result instead. Upstream changed it in:
commit 5b252f0c2f98df21fadf0f6cf189b87a0b938228
Author: Ben Hutchings <bhutchings>
Date: Thu Oct 29 07:17:09 2009 +0000
gro: Name the GRO result enumeration type
commit c7c4b3b6e976b95facbb723951bdcd554a3530a4
Author: Ben Hutchings <bhutchings>
Date: Thu Oct 29 21:36:53 2009 -0700
gro: Change all receive functions to return GRO result codes
We cannot do the same change in RHEL, because the functions are KABI. We can add new functions though.
Comment 2RHEL Program Management
2011-01-14 15:50:28 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.
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
The receive functions {napi,vlan}_gro_{frags,receive} in the RHEL kernel return NET_RX_* results. Most drivers do not care about the return value, but sfc would like to know the GRO result instead. Upstream changed it in: commit 5b252f0c2f98df21fadf0f6cf189b87a0b938228 Author: Ben Hutchings <bhutchings> Date: Thu Oct 29 07:17:09 2009 +0000 gro: Name the GRO result enumeration type commit c7c4b3b6e976b95facbb723951bdcd554a3530a4 Author: Ben Hutchings <bhutchings> Date: Thu Oct 29 21:36:53 2009 -0700 gro: Change all receive functions to return GRO result codes We cannot do the same change in RHEL, because the functions are KABI. We can add new functions though.