linux-kernel - Re: [PATCH] crypto: caam: Introduce the use of the managed version of kzalloc

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] [day] [month] [year] [list]

Message-ID: <20140620184105.GD3169@gondor.apana.org.au>
Date:	Sat, 21 Jun 2014 02:41:05 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Marek Vasut <marex@...x.de>
Cc:	Himangi Saraogi <himangi774@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
	julia.lawall@...6.fr
Subject: Re: [PATCH] crypto: caam: Introduce the use of the managed version
 of kzalloc

On Sun, Jun 01, 2014 at 06:56:41PM +0200, Marek Vasut wrote:
> On Tuesday, May 27, 2014 at 08:25:48 PM, Himangi Saraogi wrote:
> > This patch moves data allocated using kzalloc to managed data allocated
> > using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
> > functions.  Also, linux/device.h is added to make sure the devm_*()
> > routine declarations are unambiguously available. Earlier, in the probe
> > function ctrlpriv was leaked on the failure of ctrl = of_iomap(nprop, 0);
> > as well as on the failure of ctrlpriv->jrpdev = kzalloc(...); . These
> > two bugs have been fixed by the patch.
> > 
> > The following Coccinelle semantic patch was used for making the change:
> 
> Reviewed-by: Marek Vasut <marex@...x.de>

Patch applied.
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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/