[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>

authored by Swen Schillig and committed by James Bottomley 7dec9cf1 9858ae38

+4 -5
+4 -5
drivers/s390/scsi/zfcp_fc.c
··· 671 { 672 struct fc_bsg_job *job = data; 673 struct zfcp_fsf_ct_els *zfcp_ct_els = job->dd_data; 674 - int status = zfcp_ct_els->status; 675 - int reply_status; 676 677 - reply_status = status ? FC_CTELS_STATUS_REJECT : FC_CTELS_STATUS_OK; 678 - job->reply->reply_data.ctels_reply.status = reply_status; 679 - job->reply->reply_payload_rcv_len = job->reply_payload.payload_len; 680 job->job_done(job); 681 } 682
··· 671 { 672 struct fc_bsg_job *job = data; 673 struct zfcp_fsf_ct_els *zfcp_ct_els = job->dd_data; 674 + struct fc_bsg_reply *jr = job->reply; 675 676 + jr->reply_payload_rcv_len = job->reply_payload.payload_len; 677 + jr->reply_data.ctels_reply.status = FC_CTELS_STATUS_OK; 678 + jr->result = zfcp_ct_els->status ? -EIO : 0; 679 job->job_done(job); 680 } 681