Description of problem: Please add the following symbols to the kernel whitelists for RHEL 5.5: ksym(iscsi2_recv_pdu) = 10b44e99 ksym(iscsi2_conn_start) = 214f0bc1 ksym(iscsi2_host_alloc) = 3cd73055 ksym(iscsi2_destroy_endpoint) = 5ffa917c ksym(iscsi2_lookup_endpoint) = 741f4fbf ksym(vlan_gro_receive) = 7d251322 ksym(napi_gro_receive) = 9206f70a ksym(iscsi2_session_teardown) = 93bca323 ksym(iscsi2_unblock_session) = 9aeb3cac ksym(iscsi2_conn_setup) = 9eb03bf ksym(iscsi2_conn_error_event) = ae204d0d ksym(iscsi2_destroy_conn) = bbe11045 ksym(iscsi2_register_transport) = c10f18c1 ksym(iscsi2_session_setup) = d3e296b2 ksym(napi_gro_flush) = db2247bc ksym(iscsi2_block_session) = dfce5e09 ksym(iscsi2_unregister_transport) = e1387bba ksym(iscsi2_create_endpoint) = f407bef1 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Mike - can you review this list of symbols?
Matt - also, what's requiring this specifically, and what's the impact? I'm assuming you are asking for these symbols in order to build a driver kmod after 5.5, but before it is included inbox 5.6?
Yes, you are correct. The intent is to be able to build KMP packages for RHEL 5.5. Without these whitelist inclusions, KMP packages will fail to install. Our desire to build KMP packages goes beyond 5.5 though. I'm sure we'd like to supply new OOB drivers for 5.6 and later releases too. (Something about your "5.6" comment lead me to believe you thought this might be a one-off requirement.)
Are the iscsi symbols for bnx2i? Is that the only iscsi module you are packaging? Is it possible for you to distribute the iscsi layer modules (libiscsi2 and scsi_transport_iscsi2 (does not look like you need scsi_transport_iscsi and libiscsi_tcp)) with bnx2i and not whitelist the iscsi symbols? I did not add the iscsi functions to the whitelist so we could have some flexibility in what we update. We thought everyone could just update the other iscsi modules with their driver if they were going to do a kmp package. Also what are you using for iscsi tools with your package? Is it the ones from upstream/RHEL, or closer to ones getting distributed to Dell customers (the ones that uses the pci named iscsi transport)?
Matt, any insights?
Sorry for the delay. These are questions for Michael Chan, but I can field them from the KMP perspective. I'm not sure I understand why the whitelists couldn't be updated as you update the iscsi interfaces. I never took the whitelists to mean "stable API/ABI". I thought it just meant "this is the ABI for this kernel". Not having these whitelist updates means we can't create KMP packages. That would probably get some people upset.
We prefer not to distribute libiscsi2 and scsi_transport_iscsi2. But if that's the only way to go, I guess we can do that too. So, do we just install these identical modules in the updates directory then? The iscsi tools should be the version on RHEL5.5, unless we need to fix some bugs in uip. It won't be the older one using the pci name as transport. The whole purpose is so that we can update the bnx2i/cnic/bnx2/bnx2x drivers and possibly uip after RHEL5.5 ships in case we have some bug fixes or enhancements before RHEL5.6 is available.
Mike - what do you think?
(In reply to comment #6) > I'm not sure I understand why the whitelists couldn't be updated as you update > the iscsi interfaces. I never took the whitelists to mean "stable API/ABI". I > thought it just meant "this is the ABI for this kernel". > Yeah, it means a stable API. Let me think about this for a day, and get back to you. I am talking to some other vendors about what they want to do to. It seems there might be a 50/50 spit now.
I've been asked to also add the following symbols for the xen kernel. ksym(pci_enable_msi) ksym(pci_enable_msix) ksym(pci_disable_msi) ksym(pci_disable_msix)
(In reply to comment #0) > Description of problem: > > Please add the following symbols to the kernel whitelists for RHEL 5.5: > > ksym(iscsi2_recv_pdu) = 10b44e99 > ksym(iscsi2_conn_start) = 214f0bc1 > ksym(iscsi2_host_alloc) = 3cd73055 > ksym(iscsi2_destroy_endpoint) = 5ffa917c > ksym(iscsi2_lookup_endpoint) = 741f4fbf > ksym(iscsi2_session_teardown) = 93bca323 > ksym(iscsi2_unblock_session) = 9aeb3cac > ksym(iscsi2_conn_setup) = 9eb03bf > ksym(iscsi2_conn_error_event) = ae204d0d > ksym(iscsi2_destroy_conn) = bbe11045 > ksym(iscsi2_register_transport) = c10f18c1 > ksym(iscsi2_session_setup) = d3e296b2 > ksym(iscsi2_block_session) = dfce5e09 > ksym(iscsi2_unregister_transport) = e1387bba > ksym(iscsi2_create_endpoint) = f407bef1 > The iscsi ones are fine I guess.
(In reply to comment #14) > (In reply to comment #0) > > Description of problem: > > > > Please add the following symbols to the kernel whitelists for RHEL 5.5: > > > > ksym(iscsi2_recv_pdu) = 10b44e99 > > ksym(iscsi2_conn_start) = 214f0bc1 > > ksym(iscsi2_host_alloc) = 3cd73055 > > ksym(iscsi2_destroy_endpoint) = 5ffa917c > > ksym(iscsi2_lookup_endpoint) = 741f4fbf > > ksym(iscsi2_session_teardown) = 93bca323 > > ksym(iscsi2_unblock_session) = 9aeb3cac > > ksym(iscsi2_conn_setup) = 9eb03bf > > ksym(iscsi2_conn_error_event) = ae204d0d > > ksym(iscsi2_destroy_conn) = bbe11045 > > ksym(iscsi2_register_transport) = c10f18c1 > > ksym(iscsi2_session_setup) = d3e296b2 > > ksym(iscsi2_block_session) = dfce5e09 > > ksym(iscsi2_unregister_transport) = e1387bba > > ksym(iscsi2_create_endpoint) = f407bef1 > > > > The iscsi ones are fine I guess. I also wanted to say for boot, they are going to be required (or at least make it alot easier so they do not have to also carry iscsi_tcp) because of how we are not supporting bnx2i for "/" and making then use iscsi_tcp for that.
Matt, after speaking to engineering management, we don't update the whitelist post-beta, and I've been told you can work around this issue with some special tricks. I'm going to have to defer this to 5.6 since we are out of time for 5.5.
I wasn't aware there were ways to work around problems like these. Can you share what those "special tricks" are? (It isn't --force, is it?)
Matt, I wasn't sure either - Jon - do you have a pointer to a quick HOWTO or a sample on how to do this? Thanks!
Deferring this to 5.6 - but in the meantime there is planned a new release of the kmod toolset that should help address workarounds. Stay tuned....
Any word on this?
Matt - I believe Jon is on track to getting this into a post-Beta 2 snapshot.
At this time, we are unlikely to be able to whitelist the ISCSI symbols. We will let you know.
Created attachment 443430 [details] rhel56-kabi-whitelist-add-scsi-symbols.patch
Created attachment 443436 [details] rhel56-kabi-whitelist-add-net-symbols.patch
Thank you for filing your request to update our kernel ABI whitelists. We are now reviewing your request and will endeavor to provide an update in due course.
in kernel-2.6.18-223.el5 You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5 Detailed testing feedback is always welcomed.
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-0017.html