Red Hat Bugzilla – Bug 438214
[QLogic 5.2 bug] qla4xxx: Fix scsi completion, lun reset code
Last modified: 2008-05-21 11:12:12 EDT
Description of problem: 1. Remove extraneous code and fix scsi command completion code so that when the HBA indicates that the completion status is good, check the iscsi transport status prior to processing scsi status 2. Firmware requirement is to issue one marker iocb per task management command. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: The corresponding patch has already been posted to linux-scsi reflector
Created attachment 298561 [details] qla4xxx: Fix scsi completion, lun reset code
Just making sure this is a RHEL 5.3 item... correct?
If this can go into 5.2 that would be great!
I think this should be assigned to Marcus, since the code is isolated to the qla4xxx code, not anything Mike would be involved with. Marcus - I know you're pretty hammered to get everything in - what's this priority?
At this point in the 5.2 schedule, the only fixes we can take are for data corruption, system crashers, or serious regressions introduced in 5.2. Does this fit that bill?
I corresponded with David S. earlier today. This is a serious issue where one of several status that comprise the success or failure of an I/O was missed. In addition a required handshake " a marker" with the HBA is not properly performed. The problem with the status would be that a iSCSI Transport/Completions are not properly identified. This issue would cause a data corruption, because the error would be missed. Secondly the problem with the handshake would cause the device queue on the HBA to block, preventing further I/o.
in kernel-2.6.18-87.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
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 the 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/RHBA-2008-0314.html