From: YueHaibing <yuehaibing@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: <dennis.dalessandro@intel.com>, <mike.marciniszyn@intel.com>,
<dledford@redhat.com>, <linux-kernel@vger.kernel.org>,
<linux-rdma@vger.kernel.org>
Subject: Re: [PATCH -next] IB/qib: Add missing err handle for qib_user_sdma_rb_insert
Date: Thu, 3 Jan 2019 10:05:25 +0800 [thread overview]
Message-ID: <cef0e281-1d93-a0cf-03f1-b96622970567@huawei.com> (raw)
In-Reply-To: <20190102190740.GH26211@ziepe.ca>
On 2019/1/3 3:07, Jason Gunthorpe wrote:
> On Wed, Jan 02, 2019 at 08:40:50PM +0200, Leon Romanovsky wrote:
>> On Wed, Jan 02, 2019 at 10:12:24AM -0700, Jason Gunthorpe wrote:
>>> On Fri, Dec 21, 2018 at 10:19:38AM +0800, YueHaibing wrote:
>>>> It should goto err handle if qib_user_sdma_rb_insert fails,
>>>> other than success return.
>>>>
>>>> Fixes: 67810e8c3c01 ("RDMA/qib: Remove all occurrences of BUG_ON()")
>>>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>>>> drivers/infiniband/hw/qib/qib_user_sdma.c | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/drivers/infiniband/hw/qib/qib_user_sdma.c b/drivers/infiniband/hw/qib/qib_user_sdma.c
>>>> index 31c523b..e87c0a7 100644
>>>> +++ b/drivers/infiniband/hw/qib/qib_user_sdma.c
>>>> @@ -237,6 +237,8 @@ qib_user_sdma_queue_create(struct device *dev, int unit, int ctxt, int sctxt)
>>>>
>>>> ret = qib_user_sdma_rb_insert(&qib_user_sdma_rb_root,
>>>> sdma_rb_node);
>>>> + if (ret == 0)
>>>> + goto err_rb;
>>>> }
>>>
>>> This doesn't look right, what about undoing the kmalloc directly
>>> above?
>>
>> Back then, I came to conclusion that qib_user_sdma_rb_insert() never
>> returns 0. Otherwise, Dennis would see that BUG_ON() for a long time
>> ago.
>
> It fails if the index is in the RB tree, which would indicate a
> programming bug.
>
> The way to replace the BUG_ON is something like:
>
Oh, yes, I forget kfree this mem.
> if (WARN_ON(ret == 0)) {
> kfree()
> goto err_rb;
> }
>
> Jason
>
> .
>
next prev parent reply other threads:[~2019-01-03 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 2:19 YueHaibing
2019-01-02 17:12 ` Jason Gunthorpe
2019-01-02 18:40 ` Leon Romanovsky
2019-01-02 19:07 ` Jason Gunthorpe
2019-01-02 19:22 ` Leon Romanovsky
2019-01-04 6:08 ` YueHaibing
2019-01-03 2:05 ` YueHaibing [this message]
2019-01-04 18:39 ` Marciniszyn, Mike
2019-01-04 22:38 ` Jason Gunthorpe
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=cef0e281-1d93-a0cf-03f1-b96622970567@huawei.com \
--to=yuehaibing@huawei.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.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
all inboxes | Powered by JetHome®