As a user of bsg-lib the SAS transport should not poke into request
internals but use the bsg_job fields instead.

Signed-off-by: Christoph Hellwig <h...@lst.de>
---
 drivers/scsi/scsi_transport_sas.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/scsi/scsi_transport_sas.c 
b/drivers/scsi/scsi_transport_sas.c
index 319dff970237..736a1f4f9676 100644
--- a/drivers/scsi/scsi_transport_sas.c
+++ b/drivers/scsi/scsi_transport_sas.c
@@ -177,7 +177,7 @@ static int sas_smp_dispatch(struct bsg_job *job)
        if (!scsi_is_host_device(job->dev))
                rphy = dev_to_rphy(job->dev);
 
-       if (!job->req->next_rq) {
+       if (!job->reply_payload.payload_len) {
                dev_warn(job->dev, "space for a smp response is missing\n");
                bsg_job_done(job, -EINVAL, 0);
                return 0;
-- 
2.14.1

Reply via email to