Description of problem: 1. make sure cnic dev is registered: When using iface, bnx2i was unable to offload further connections after all active sessions are logged out. bnx2i will unregister the device from cnic when the last connection is torn down. Next call to ep_connect() will fail because the device is not registered. This issue is not seen if shost == NULL is passed to ep_connect() call because in that case bnx2i will registers all known devices with cnic before doing a route look-up. When shost != NULL, bnx2i knows the device on which to offload the connection and has to register this device before attempting to offload the connection 2. fix libiscsi eh abort locking iscsi_eh_abort needs to grab the session lock and disable bhs, because the session lock can be taken from a timer or softirq. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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.
Created attachment 354542 [details] fix bnx2i host setup and eh abort locking fix bnx2i host setup and eh abort locking
in kernel-2.6.18-159.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 Please do NOT transition this bugzilla state to VERIFIED until our QE team has sent specific instructions indicating when to do so. However feel free to provide a comment indicating that this fix has been verified.
I confirmed the patch : linux-2.6-scsi-bnx2i-fix-host-setup-and-libiscsi-abort-locking.patch was included in kernel: kernel-2.6.18-160.el5.src.rpm set SanityOnly
Testing 2.6.18-162.el5 now. So far so good, I'll post issues if I find any.
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-2009-1243.html