Bug 525534
| Summary: | [Emulex 5.5 feat] Whitelist updates for be2net | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | laurie barry <laurie.barry> |
| Component: | kernel | Assignee: | Jon Masters <jcm> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.5 | CC: | agospoda, andriusb, ivecera, james.smart, sean.murphy, subbu.seetharaman, vaios.papadimitriou |
| Target Milestone: | rc | Keywords: | FutureFeature, OtherQA |
| Target Release: | 5.5 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-09-25 16:29:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
laurie barry
2009-09-24 17:55:10 UTC
I'm assuming running the script from: http://driverupdateprogram.com/downloads/abi_check.py will yield the same results for identifying the offending symbols? Yes. # ./abi_check.py /lib/modules/2.6.18-128.el5/extra/be2net.ko Red Hat Enterprise Linux 5 ABI Checker -------------------------------------- ABI Checker version: 1.2 Module: be2net.ko Kernel: 2.6.18-128.el5 Whitelist: /usr/src/kernels/2.6.18-128.el5-x86_64/kabi_whitelist WARNING: The following symbols are used by your module WARNING: and are not on the ABI whitelist. symbol: lro_flush_all symbol: lro_receive_frags symbol: lro_vlan_hwaccel_receive_frags [root@kettle extra]# Thanks Vaios - just wanted to double check to make sure the tool output matches what you were seeing when you tried to install the kernel. Emulex: Any reason why LSO is being used to begin? GRO was added in RHEL 5.4 and upstream be2net is GRO I believe as well... You are right Andrius. Unlike be2net in RH 5.4, this be2net driver uses GRO instead of LRO and this is not an issue for be2net. We can close this bug. Thanks. Subbu Will do - I'm assuming this is also the case as well upstream for RHEL 6, correct? May close those as well? Yes, GRO in upstream and RH6 also. Subbu |