All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ewan D. Milne" <emilne@redhat.com>
To: Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	linux-scsi@vger.kernel.org, stable@vger.kernel.org,
	Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH 2/4] hptiop: fix calls to dma_set_mask_and_coherent()
Date: Wed, 13 Feb 2019 13:52:19 -0500	[thread overview]
Message-ID: <bd14fa79fcf91334a19c034fbff9cabc34862ed9.camel@redhat.com> (raw)
In-Reply-To: <20190213114234.67275-3-hare@suse.de>

The patch subject line is incorrect, the driver was changed
to call dma_set_mask(), not dma_set_mask_and_coherent().
Also see comments below re: the patch description.  The
code itself looks fine.

-Ewan

On Wed, 2019-02-13 at 12:42 +0100, Hannes Reinecke wrote:
> 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.  This resulted in NVMe/FC connections failing due
                         ------------------------------------------------
> to corrupted data buffers, and various other SCSI/FCP I/O errors.
-------------------------------------------------------------------

The last sentence should be removed from the patch description.  And the
second-to-last sentence should say something like "..the first DMA mask...".

> 
> Fixes: 453cd3700ca3 ("scsi: hptiop: use dma_set_mask")
> Cc: <stable@vger.kernel.org>
> Suggested-by: Ewan D. Milne <emilne@redhat.com>
> Signed-off-by: Hannes Reinecke <hare@suse.com>
> ---
>  drivers/scsi/hptiop.c | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/scsi/hptiop.c b/drivers/scsi/hptiop.c
> index 3eedfd4f8f57..251c084a6ff0 100644
> --- a/drivers/scsi/hptiop.c
> +++ b/drivers/scsi/hptiop.c
> @@ -1292,6 +1292,7 @@ static int hptiop_probe(struct pci_dev *pcidev, const struct pci_device_id *id)
>  	dma_addr_t start_phy;
>  	void *start_virt;
>  	u32 offset, i, req_size;
> +	int rc;
>  
>  	dprintk("hptiop_probe(%p)\n", pcidev);
>  
> @@ -1308,9 +1309,12 @@ static int hptiop_probe(struct pci_dev *pcidev, const struct pci_device_id *id)
>  
>  	/* Enable 64bit DMA if possible */
>  	iop_ops = (struct hptiop_adapter_ops *)id->driver_data;
> -	if (dma_set_mask(&pcidev->dev,
> -			 DMA_BIT_MASK(iop_ops->hw_dma_bit_mask)) ||
> -	    dma_set_mask(&pcidev->dev, DMA_BIT_MASK(32))) {
> +	rc = dma_set_mask(&pcidev->dev,
> +			  DMA_BIT_MASK(iop_ops->hw_dma_bit_mask));
> +	if (rc)
> +		rc = dma_set_mask(&pcidev->dev, DMA_BIT_MASK(32));
> +
> +	if (rc) {
>  		printk(KERN_ERR "hptiop: fail to set dma_mask\n");
>  		goto disable_pci_device;
>  	}

  reply	other threads:[~2019-02-13 18:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190213114234.67275-1-hare@suse.de>
2019-02-13 11:42 ` [PATCH 1/4] lpfc: fix calls to dma_set_mask_and_coherent() Hannes Reinecke
2019-02-13 18:52   ` Ewan D. Milne
2019-02-13 11:42 ` [PATCH 2/4] hptiop: " Hannes Reinecke
2019-02-13 18:52   ` Ewan D. Milne [this message]
2019-02-13 11:42 ` [PATCH 3/4] bfa: " Hannes Reinecke
2019-02-13 18:52   ` Ewan D. Milne
2019-02-13 21:35   ` kbuild test robot
2019-02-13 21:35     ` kbuild test robot
2019-02-18  6:23   ` Dan Carpenter
2019-02-18  6:23     ` Dan Carpenter
2019-02-13 11:42 ` [PATCH 4/4] hisi_sas: " Hannes Reinecke
2019-02-13 11:51   ` John Garry
2019-02-13 11:51     ` John Garry
2019-02-13 18:52   ` Ewan D. 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=bd14fa79fcf91334a19c034fbff9cabc34862ed9.camel@redhat.com \
    --to=emilne@redhat.com \
    --cc=hare@suse.com \
    --cc=hare@suse.de \
    --cc=hch@lst.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.