[SCSI] zfcp: Report FC BSG errors in correct field
The status FC_CTELS_STATUS_REJECT for all FC BSG errors is not appropriate. Instead, report -EIO in the result field if there was a problem in zfcp with the FC BSG request. If the request is good from our point of view, report result 0, status FC_CTELS_STATUS_OK and let userspace read the Accept or Reject from the payload (as documented in scsi_bsg_fc.h). Signed-off-by: Swen Schillig <swen@vnet.ibm.com> Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
This commit is contained in:
parent
9858ae3801
commit
7dec9cf1df
|
@ -671,12 +671,11 @@ static void zfcp_fc_ct_els_job_handler(void *data)
|
|||
{
|
||||
struct fc_bsg_job *job = data;
|
||||
struct zfcp_fsf_ct_els *zfcp_ct_els = job->dd_data;
|
||||
int status = zfcp_ct_els->status;
|
||||
int reply_status;
|
||||
struct fc_bsg_reply *jr = job->reply;
|
||||
|
||||
reply_status = status ? FC_CTELS_STATUS_REJECT : FC_CTELS_STATUS_OK;
|
||||
job->reply->reply_data.ctels_reply.status = reply_status;
|
||||
job->reply->reply_payload_rcv_len = job->reply_payload.payload_len;
|
||||
jr->reply_payload_rcv_len = job->reply_payload.payload_len;
|
||||
jr->reply_data.ctels_reply.status = FC_CTELS_STATUS_OK;
|
||||
jr->result = zfcp_ct_els->status ? -EIO : 0;
|
||||
job->job_done(job);
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue