linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Droneaud <ydroneaud@opteya.com>
To: Julia Lawall <Julia.Lawall@lip6.fr>,
	Gilles Muller <Gilles.Muller@lip6.fr>,
	Nicolas Palix <nicolas.palix@imag.fr>,
	Michal Marek <mmarek@suse.com>
Cc: Tejun Heo <tj@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org,
	Yann Droneaud <ydroneaud@opteya.com>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Eli Billauer <eli.billauer@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Himangi Saraogi <himangi774@gmail.com>,
	Joe Perches <joe@perches.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Manish Badarkhe <badarkhe.manish@gmail.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Wolfram Sang <w.sang@pengutronix.de>
Subject: [PATCH 0/3] coccinelle: catchup on memory allocation functions
Date: Tue, 16 Feb 2016 18:01:31 +0100	[thread overview]
Message-ID: <cover.1455638829.git.ydroneaud@opteya.com> (raw)

Hi,

Please find few patches that remove coccicheck's blindness
regarding the following functions:
- kzfree()
- krealloc()
- __krealloc()
- devm_kmalloc()
- devm_kvasprintf()
- devm_kasprintf()
- devm_kmalloc_array()
- devm_kcalloc()
- devm_kstrdup()
- devm_kmemdup()
- devm_get_free_pages()
- free_pages()
- free_page()

I've ran coccicheck on drivers/staging and found no new issue,
which is great, but that questions those patches' usefulness,
YMMV.

Regards.

Yann Droneaud (3):
  coccinelle: also catch kzfree() issues
  coccinelle: recognize more devm_* memory allocation functions
  coccinelle: catch krealloc() on devm_*() allocated memory

 scripts/coccinelle/free/devm_free.cocci | 26 ++++++++++++++++++++++++++
 scripts/coccinelle/free/kfree.cocci     |  3 +++
 scripts/coccinelle/free/kfreeaddr.cocci |  6 +++++-
 3 files changed, 34 insertions(+), 1 deletion(-)

-- 
2.5.0

             reply	other threads:[~2016-02-16 17:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 17:01 Yann Droneaud [this message]
2016-02-16 17:06 ` [PATCH 1/3] coccinelle: also catch kzfree() issues Yann Droneaud
2016-02-16 17:16   ` Julia Lawall
2016-02-16 20:02     ` SF Markus Elfring
2016-02-16 20:17       ` Julia Lawall
2016-02-16 20:22         ` SF Markus Elfring
2016-02-22 14:09     ` [PATCHv1 1/3] " Yann Droneaud
2016-02-22 14:20       ` Julia Lawall
2016-02-22 15:24         ` Yann Droneaud
2016-02-16 17:06 ` [PATCH 2/3] coccinelle: recognize more devm_* memory allocation functions Yann Droneaud
2016-02-16 17:18   ` Julia Lawall
2016-02-16 17:06 ` [PATCH 3/3] coccinelle: catch krealloc() on devm_*() allocated memory Yann Droneaud
2016-02-16 17:19   ` Julia Lawall

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=cover.1455638829.git.ydroneaud@opteya.com \
    --to=ydroneaud@opteya.com \
    --cc=Gilles.Muller@lip6.fr \
    --cc=Julia.Lawall@lip6.fr \
    --cc=badarkhe.manish@gmail.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=daniel.thompson@linaro.org \
    --cc=eli.billauer@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=himangi774@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=nicolas.palix@imag.fr \
    --cc=penberg@cs.helsinki.fi \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tj@kernel.org \
    --cc=w.sang@pengutronix.de \
    /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).