linux-kernel - Re: [PATCH] thermal: power_allocator: allocate with kcalloc what you free with kfree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150827154936.GH5653@e104805>
Date:	Thu, 27 Aug 2015 16:49:37 +0100
From:	Javi Merino <javi.merino@....com>
To:	"edubezval@...il.com" <edubezval@...il.com>
Cc:	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCH] thermal: power_allocator: allocate with kcalloc what you
 free with kfree

On Tue, Aug 25, 2015 at 07:22:35PM +0100, Javi Merino wrote:
> Commit cf736ea6f902 ("thermal: power_allocator: do not use devm*
> interfaces") forgot to change a devm_kcalloc() to just kcalloc(), but
> it's corresponding devm_kfree() was changed to kfree().  Allocate with
> kcalloc() to match the kfree().
> 
> Fixes: cf736ea6f902 ("thermal: power_allocator: do not use devm* interfaces")
> Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>
> Cc: Eduardo Valentin <edubezval@...il.com>
> Cc: Zhang Rui <rui.zhang@...el.com>
> Signed-off-by: Javi Merino <javi.merino@....com>
> ---
> 
> Can this be merged for 4.2, please?  I'm having memory problems with
> 4.2-rc8 because of this.

Please merge this for 4.2 or revert cf736ea6f902 ("thermal:
power_allocator: do not use devm* interfaces")
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/