From: Leon Romanovsky <leon@kernel.org>
To: Weihang Li <liweihang@huawei.com>
Cc: dledford@redhat.com, jgg@nvidia.com, linux-rdma@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH for-next] RDMA/hns: Fix memory corruption when allocating XRCDN
Date: Sat, 20 Mar 2021 11:32:59 +0200 [thread overview]
Message-ID: <YFXBSyUI/J8uMoxH@unreal> (raw)
In-Reply-To: <1616143536-24874-1-git-send-email-liweihang@huawei.com>
On Fri, Mar 19, 2021 at 04:45:36PM +0800, Weihang Li wrote:
> It's incorrect to cast the type of pointer to xrcdn from (u32 *) to
> (unsigned long *), then pass it into hns_roce_bitmap_alloc(), this will
> lead to a memory corruption.
>
> Fixes: 32548870d438 ("RDMA/hns: Add support for XRC on HIP09")
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Weihang Li <liweihang@huawei.com>
> ---
> drivers/infiniband/hw/hns/hns_roce_pd.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/hw/hns/hns_roce_pd.c b/drivers/infiniband/hw/hns/hns_roce_pd.c
> index 3ca51ce..16d6b69 100644
> --- a/drivers/infiniband/hw/hns/hns_roce_pd.c
> +++ b/drivers/infiniband/hw/hns/hns_roce_pd.c
> @@ -140,8 +140,14 @@ void hns_roce_cleanup_uar_table(struct hns_roce_dev *hr_dev)
>
> static int hns_roce_xrcd_alloc(struct hns_roce_dev *hr_dev, u32 *xrcdn)
> {
> - return hns_roce_bitmap_alloc(&hr_dev->xrcd_bitmap,
> - (unsigned long *)xrcdn);
> + unsigned long obj;
> + int ret;
> +
> + ret = hns_roce_bitmap_alloc(&hr_dev->xrcd_bitmap, &obj);
> +
> + *xrcdn = (u32)obj;
NIT, it will be safer if you don't set set xrcdn after hns_roce_bitmap_alloc() failed.
Thanks
> +
> + return ret;
> }
>
> static void hns_roce_xrcd_free(struct hns_roce_dev *hr_dev,
> --
> 2.8.1
>
next prev parent reply other threads:[~2021-03-20 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 8:45 [PATCH for-next] RDMA/hns: Fix memory corruption when allocating XRCDN Weihang Li
2021-03-20 9:32 ` Leon Romanovsky [this message]
2021-03-22 2:00 ` liweihang
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=YFXBSyUI/J8uMoxH@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liweihang@huawei.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