From: Julia Lawall <julia.lawall@lip6.fr>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: Julia Lawall <Julia.Lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <mmarek@suse.com>, Tejun Heo <tj@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH 3/3] coccinelle: catch krealloc() on devm_*() allocated memory
Date: Tue, 16 Feb 2016 18:19:52 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1602161819340.2685@hadrien> (raw)
In-Reply-To: <5783128fc07898adc6860a398fc4f4e0893bc91a.1455638829.git.ydroneaud@opteya.com>
On Tue, 16 Feb 2016, Yann Droneaud wrote:
> krealloc() must not be used against devm_*() allocated
> memory regions:
>
> - if a bigger memory is to be allocated, krealloc() and
> __krealloc() could return a different pointer than the
> one given to them, creating a memory region which is not
> managed, thus it will not be automatically released on
> device removal.
>
> - if a bigger memory is to be allocated, krealloc() could
> kfree() the managed memory region which is passed to it.
> The old pointer is left registered as a resource for the
> device. On device removal, this dangling pointer will be
> used and an unrelated memory region could be released.
>
> - if the requested size is equal to 0, krealloc() can also
> just behave like kfree(). Here too, the old pointer is
> kept associated with the device. On device removal, this
> invalid pointer will be used and an unrelated memory
> region could be released.
>
> For all these reasons, krealloc() must not be used on a
> pointer returned by devm_*() functions.
>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Pekka Enberg <penberg@cs.helsinki.fi>
> Signed-off-by: Yann Droneaud <ydroneaud@opteya.com>
Acked-by: Julia Lawall <julia.lawall@lip6.fr>
> ---
> scripts/coccinelle/free/devm_free.cocci | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/scripts/coccinelle/free/devm_free.cocci b/scripts/coccinelle/free/devm_free.cocci
> index 3794cd97494b..c990d2c7ee16 100644
> --- a/scripts/coccinelle/free/devm_free.cocci
> +++ b/scripts/coccinelle/free/devm_free.cocci
> @@ -66,6 +66,10 @@ position p;
> |
> * kzfree@p(x)
> |
> +* __krealloc@p(x, ...)
> +|
> +* krealloc@p(x, ...)
> +|
> * free_pages@p(x, ...)
> |
> * free_page@p(x)
> --
> 2.5.0
>
>
prev parent reply other threads:[~2016-02-16 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 17:01 [PATCH 0/3] coccinelle: catchup on memory allocation functions Yann Droneaud
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 [this message]
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=alpine.DEB.2.10.1602161819340.2685@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.fr \
--cc=penberg@cs.helsinki.fi \
--cc=tj@kernel.org \
--cc=ydroneaud@opteya.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®