cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: linux-rdma@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Coccinelle <cocci@systeme.lip6.fr>,
	Dennis Dalessandro <dennis.dalessandro@intel.com>,
	Doug Ledford <dledford@redhat.com>,
	Gal Pressman <galpress@amazon.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Leon Romanovsky <leonro@mellanox.com>,
	Lijun Ou <oulijun@huawei.com>, Wei Hu <xavier.huwei@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [Cocci] RDMA/hns: Checking two kfree() calls in hns_roce_v1_release_lp_qp()
Date: Fri, 8 Nov 2019 16:40:21 +0100	[thread overview]
Message-ID: <0e7f1ff5-eb17-530e-45e9-920ce183a10d@web.de> (raw)

Hello,

A coccicheck run provided information like the following.

./drivers/infiniband/hw/hns/hns_roce_hw_v1.c:901:1-6: ERROR: invalid free of structure field
./drivers/infiniband/hw/hns/hns_roce_hw_v1.c:903:1-6: ERROR: invalid free of structure field

Generated by: scripts/coccinelle/free/kfreeaddr.cocci

See also:
* Commit e39afe3d6dbd908d8fd189571a3c1561088a86c2
  ("RDMA: Convert CQ allocations to be under core responsibility" from 2019-06-11)

* Commit 619122be3d40c835eb5fad9e326780909926495d
  ("RDMA/hns: Fix PD memory leak for internal allocation" from 2019-05-21)


How would you like to handle such details further?

Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

                 reply	other threads:[~2019-11-08 15:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0e7f1ff5-eb17-530e-45e9-920ce183a10d@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@systeme.lip6.fr \
    --cc=dennis.dalessandro@intel.com \
    --cc=dledford@redhat.com \
    --cc=galpress@amazon.com \
    --cc=jgg@ziepe.ca \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=leonro@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=oulijun@huawei.com \
    --cc=xavier.huwei@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;
as well as URLs for NNTP newsgroup(s).