linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: QLogic-Storage-Upstream@qlogic.com,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	clang-built-linux@googlegroups.com
Subject: Re: [PATCH] scsi: qla4xxx: Don't call dma_free_coherent without dma_alloc_coherent
Date: Thu, 7 Mar 2019 10:49:17 -0800	[thread overview]
Message-ID: <CAKwvOdmFduT6bd7=xAsC0YcaJZL6MUUoMzmb2dW9YMGD0x4eqg@mail.gmail.com> (raw)
In-Reply-To: <20190307184125.21419-1-natechancellor@gmail.com>

On Thu, Mar 7, 2019 at 10:41 AM Nathan Chancellor
<natechancellor@gmail.com> wrote:
>
> When building with -Wsometimes-uninitialized, Clang warns:
>
> drivers/scsi/qla4xxx/ql4_os.c:5915:7: warning: variable 'buf_dma' is
> used uninitialized whenever 'if' condition is false
> [-Wsometimes-uninitialized]
>
> buf_dma is initialized by dma_alloc_coherent, which is only called in
> the middle conditional statement. Use that same conditional to call
> dma_free_coherent so that buf_dma is always initialized when used.
>
> Fixes: 2a991c215978 ("[SCSI] qla4xxx: Boot from SAN support for open-iscsi")
> Link: https://github.com/ClangBuiltLinux/linux/issues/391
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
>  drivers/scsi/qla4xxx/ql4_os.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/qla4xxx/ql4_os.c b/drivers/scsi/qla4xxx/ql4_os.c
> index 16a18d5d856f..88bb52456efd 100644
> --- a/drivers/scsi/qla4xxx/ql4_os.c
> +++ b/drivers/scsi/qla4xxx/ql4_os.c
> @@ -5982,7 +5982,8 @@ static int get_fw_boot_info(struct scsi_qla_host *ha, uint16_t ddb_index[])
>                           ddb_index[1]));
>
>  exit_boot_info_free:
> -       dma_free_coherent(&ha->pdev->dev, size, buf, buf_dma);
> +       if (is_qla80XX(ha))
> +               dma_free_coherent(&ha->pdev->dev, size, buf, buf_dma);

Very tricky code flow to follow in this function, but this patch makes
sense upon closer inspection.  Thanks for the patch Nathan
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>

-- 
Thanks,
~Nick Desaulniers

  reply	other threads:[~2019-03-07 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 18:41 [PATCH] scsi: qla4xxx: Don't call dma_free_coherent without dma_alloc_coherent Nathan Chancellor
2019-03-07 18:49 ` Nick Desaulniers [this message]
2019-03-07 23:15 ` [PATCH v2] scsi: qla4xxx: Don't call dma_free_coherent when buf is NULL Nathan Chancellor
2019-03-08 21:16   ` Nick Desaulniers
2019-03-22 14:25     ` Arnd Bergmann

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='CAKwvOdmFduT6bd7=xAsC0YcaJZL6MUUoMzmb2dW9YMGD0x4eqg@mail.gmail.com' \
    --to=ndesaulniers@google.com \
    --cc=QLogic-Storage-Upstream@qlogic.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=natechancellor@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).