drivers: scsi: megaraid: Add missing check for dma_set_mask
Subsystems (3)
PATCH 1/1 drivers: scsi: megaraid: Add missing check for dma_set_mask
pdev->dev cannot perform DMA properly if dma_set_mask() returns non-zero. Add check for dma_set_mask() and return the error if it fails.
--- drivers/scsi/megaraid.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/scsi/megaraid.c +4 -2
@@ -4406,10 +4406,12 @@ megaraid_probe_one(struct pci_dev *pdev, const struct pci_device_id *id)/* Set the Mode of addressing to 64 bit if we can */ if ((adapter->flag &BOARD_64BIT ) && (sizeof (dma_addr_t) ==8 )) { -dma_set_mask (&pdev->dev,DMA_BIT_MASK (64 )); +if (dma_set_mask (&pdev->dev,DMA_BIT_MASK (64 ))) + goto out_free_mbox; adapter->has_64bit_addr =1 ; }else { -dma_set_mask (&pdev->dev,DMA_BIT_MASK (32 )); +if (dma_set_mask (&pdev->dev,DMA_BIT_MASK (32 ))) + goto out_free_mbox; adapter->has_64bit_addr =0 ; }
Signature · 1 line
2.25.1
Quoted 1 line
pdev->devcannot perform DMA properly ifdma_set_mask()returns non-zero.
Can a wording approach (like the following) become a part of a better change description?
Direct memory access can not be properly performed any more after a dma_set_mask() call failed.
Quoted 1 line
Add check for
dma_set_mask()
How do you think about to avoid a repeated reference to a function name?
Quoted 1 line
return the error if it fails.
How can this happen after you did not store the return value (in the local variable “error”) for further usage (according to your proposed source code adjustment)?
…
Quoted 1 line
Signed-off-by Haoxiang Li <[email protected]>
I find it interesting that another personal name is presented here. I noticed that some patches were published with the name “Ma Ke” previously. How will requirements be resolved for the Developer's Certificate of Origin?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc6#n398
How do you think about to use a summary phrase like “Complete error handling in megaraid_probe_one()”?
Regards,
Markus