All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ewan Milne <emilne@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 4/8] 3w-sas: fix calls to dma_set_mask_and_coherent()
Date: Mon, 25 Feb 2019 19:32:26 -0500 (EST)	[thread overview]
Message-ID: <1659665098.3869910.1551141146893.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190218073426.111853-5-hare@suse.de>

The change to use dma_set_mask_and_coherent() incorrectly made a second
call with the 32 bit DMA mask value when the call with the 64 bit DMA
mask value succeeded.

Fixes: 3a21986f1a59 ("scsi: aic94xx: fully convert to the generic DMA API")
Cc: <stable@vger.kernel.org>
Signed-off-by: Hannes Reinecke <hare@suse.com>
---
 drivers/scsi/aic94xx/aic94xx_init.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/drivers/scsi/aic94xx/aic94xx_init.c b/drivers/scsi/aic94xx/aic94xx_init.c
index f83f79b07b50..d41f645e8454 100644
--- a/drivers/scsi/aic94xx/aic94xx_init.c
+++ b/drivers/scsi/aic94xx/aic94xx_init.c
@@ -769,9 +769,11 @@ static int asd_pci_probe(struct pci_dev *dev, const struct pci_device_id *id)
 	if (err)
 		goto Err_remove;
 
-	err = -ENODEV;
-	if (dma_set_mask_and_coherent(&dev->dev, DMA_BIT_MASK(64)) ||
-	    dma_set_mask_and_coherent(&dev->dev, DMA_BIT_MASK(32))) {
+	err = dma_set_mask_and_coherent(&dev->dev, DMA_BIT_MASK(64));
+	if (err)
+		err = dma_set_mask_and_coherent(&dev->dev, DMA_BIT_MASK(32));
+	if (err) {
+		err = -ENODEV;
 		asd_printk("no suitable DMA mask for %s\n", pci_name(dev));
 		goto Err_remove;
 	}
-- 
2.16.4

The patch subject should be "aic94xx:", Martin, can you fix this up?

Reviewed-by: Ewan D. Milne <emilne@redhat.com>

  parent reply	other threads:[~2019-02-26  0:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190218073426.111853-1-hare@suse.de>
2019-02-18  7:34 ` [PATCH 1/8] lpfc: fix calls to dma_set_mask_and_coherent() Hannes Reinecke
2019-02-18  9:24   ` Christoph Hellwig
2019-02-26  0:29   ` Ewan Milne
2019-02-18  7:34 ` [PATCH 2/8] 3w-9xxx: " Hannes Reinecke
2019-02-18  9:24   ` Christoph Hellwig
2019-02-26  0:30   ` Ewan Milne
2019-02-18  7:34 ` [PATCH 3/8] 3w-sas: " Hannes Reinecke
2019-02-18  9:24   ` Christoph Hellwig
2019-02-26  0:30   ` Ewan Milne
2019-02-18  7:34 ` [PATCH 4/8] " Hannes Reinecke
2019-02-18  9:25   ` Christoph Hellwig
2019-02-26  0:32   ` Ewan Milne [this message]
2019-02-18  7:34 ` [PATCH 5/8] bfa: " Hannes Reinecke
2019-02-18  9:25   ` Christoph Hellwig
2019-02-26  0:34   ` Ewan Milne
2019-02-18  7:34 ` [PATCH 6/8] csiostor: " Hannes Reinecke
2019-02-18  9:25   ` Christoph Hellwig
2019-02-26  0:35   ` Ewan Milne
2019-02-18  7:34 ` [PATCH 7/8] hisi_sas: " Hannes Reinecke
2019-02-18  9:24   ` John Garry
2019-02-18  9:24     ` John Garry
2019-02-18  9:26   ` Christoph Hellwig
2019-02-26  0:37   ` Ewan Milne
2019-02-18  7:34 ` [PATCH 8/8] hptiop: fix calls to dma_set_mask() Hannes Reinecke
2019-02-18  9:26   ` Christoph Hellwig
2019-02-26  0:38   ` Ewan Milne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1659665098.3869910.1551141146893.JavaMail.zimbra@redhat.com \
    --to=emilne@redhat.com \
    --cc=hare@suse.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.