From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Alex Dewar <alex.dewar90@gmail.com>,
Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/ucma: Fix resource leak on error path
Date: Wed, 2 Sep 2020 19:40:58 -0500 [thread overview]
Message-ID: <0204eb72-8024-e6fc-800c-bd7e6ff94da7@embeddedor.com> (raw)
In-Reply-To: <20200903003242.GL24045@ziepe.ca>
On 9/2/20 19:32, Jason Gunthorpe wrote:
>>> Addresses-Coverity: ("Resource leak")
>>
>> If you are using a public Coverity scan, please also include the Coverity ID.
>> In this case ID 1496814, something like:
>>
>> Addresses-Coverity-ID: 1496814 ("Resource leak")
>
> Thanks, I fixed it up
>
Awesome. :)
Thanks, Jason.
--
Gustavo
next prev parent reply other threads:[~2020-09-03 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 16:24 [PATCH] RDMA/ucma: Fix resource leak on error path Alex Dewar
2020-09-02 20:10 ` Jason Gunthorpe
2020-09-03 0:34 ` Gustavo A. R. Silva
2020-09-03 0:32 ` Jason Gunthorpe
2020-09-03 0:40 ` Gustavo A. R. Silva [this message]
2020-09-03 9:35 ` Alex Dewar
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=0204eb72-8024-e6fc-800c-bd7e6ff94da7@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=alex.dewar90@gmail.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 \
/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