public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-next] IB/mthca: Check validity of output parameter pointer
Date: Tue, 18 Apr 2017 16:48:56 +0300	[thread overview]
Message-ID: <20170418134855.GA3490@yuval-lap> (raw)
In-Reply-To: <20170415154725.17559-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

On Sat, Apr 15, 2017 at 06:47:25PM +0300, Leon Romanovsky wrote:
> The mthca driver didn't check supplied pointer to functions
> mthca_cmd_poll() and mthca_cmd_wait(). This caused to the following
> smatch errors:
> 
> drivers/infiniband/hw/mthca/mthca_cmd.c:371 mthca_cmd_poll() error: we previously assumed 'out_param' could be null (see line 353)
> drivers/infiniband/hw/mthca/mthca_cmd.c:454 mthca_cmd_wait() error: we previously assumed 'out_param' could be null (see line 432)
> 
> In reality all callers of these functions are setting out_is_imm
> flag are providing pointer too. However it is better to check
> again to remove smatch errors to achieve warning free subsystem.
> 
> Signed-off-by: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> ---
>  Based on k.o/for-4.12 branch.
> ---
>  drivers/infiniband/hw/mthca/mthca_cmd.c | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/infiniband/hw/mthca/mthca_cmd.c b/drivers/infiniband/hw/mthca/mthca_cmd.c
> index c7f49bbb0c72..9d83a53c0c67 100644
> --- a/drivers/infiniband/hw/mthca/mthca_cmd.c
> +++ b/drivers/infiniband/hw/mthca/mthca_cmd.c
> @@ -367,12 +367,16 @@ static int mthca_cmd_poll(struct mthca_dev *dev,
>  		goto out;
>  	}
> 
> -	if (out_is_imm)
> +	if (out_is_imm && out_param) {
>  		*out_param =
>  			(u64) be32_to_cpu((__force __be32)
>  					  __raw_readl(dev->hcr + HCR_OUT_PARAM_OFFSET)) << 32 |
>  			(u64) be32_to_cpu((__force __be32)
>  					  __raw_readl(dev->hcr + HCR_OUT_PARAM_OFFSET + 4));
> +	} else if (out_is_imm) {
> +		err = -EINVAL;
> +		goto out;

So if this is a good reason to fail the function - how about doing this
validation before triggering HW operation (mthca_cmd_post)?

> +	}
> 
>  	status = be32_to_cpu((__force __be32) __raw_readl(dev->hcr + HCR_STATUS_OFFSET)) >> 24;
>  	if (status) {
> @@ -450,8 +454,12 @@ static int mthca_cmd_wait(struct mthca_dev *dev,
>  		err = mthca_status_to_errno(context->status);
>  	}
> 
> -	if (out_is_imm)
> +	if (out_is_imm && out_param) {
>  		*out_param = context->out_param;
> +	} else if (out_is_imm) {
> +		err = -EINVAL;

Ditto

> +		goto out;
> +	}
> 
>  out:
>  	spin_lock(&dev->cmd.context_lock);
> --
> 2.12.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-04-18 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15 15:47 [PATCH rdma-next] IB/mthca: Check validity of output parameter pointer Leon Romanovsky
     [not found] ` <20170415154725.17559-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-04-18 13:48   ` Yuval Shaia [this message]
2017-04-18 14:02     ` Leon Romanovsky
2017-04-24 16:28   ` Doug Ledford

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=20170418134855.GA3490@yuval-lap \
    --to=yuval.shaia-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox