On Sat, Dec 08, 2012 at 07:01:20PM +0100, Julia Lawall wrote:
> From: Julia Lawall
>
> Using kfree to free data allocated with devm_kzalloc causes double frees.
Ugh, actually this doesn't merge down very well against -next at all,
can you regenerate against current code please?
--
To unsubscribe
On Mon, Dec 10, 2012 at 07:10:16AM +0100, Julia Lawall wrote:
> Sorry, I just resent the patch as is. 1 and 2 were I guess applied,
> because I odn't findthe problem any more.
It looks like this is what happened the first time round as well - I
only got patch 3 but it was flagged as part of a th
On Mon, 10 Dec 2012, Mark Brown wrote:
On Sat, Dec 08, 2012 at 07:01:20PM +0100, Julia Lawall wrote:
The kfrees were introduced in b761c0ca.
I sent this a few months ago, and I still think it should be applied...
I'm missing patches 1 and 2?
Sorry, I just resent the patch as is. 1 and 2 w
On Sat, Dec 08, 2012 at 07:01:20PM +0100, Julia Lawall wrote:
> The kfrees were introduced in b761c0ca.
> I sent this a few months ago, and I still think it should be applied...
I'm missing patches 1 and 2?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Sat, Aug 04, 2012 at 02:00:32PM +0200, Julia Lawall wrote:
> From: Julia Lawall
>
> Using kfree to free data allocated with devm_kzalloc causes double frees.
>
> The semantic patch that fixes this problem is as follows:
> (http://coccinelle.lip6.fr/)
Might it make more sense to devm_kfree()
5 matches
Mail list logo