From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752672Ab1LZQTV (ORCPT ); Mon, 26 Dec 2011 11:19:21 -0500 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:49435 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751032Ab1LZQTR (ORCPT ); Mon, 26 Dec 2011 11:19:17 -0500 Date: Mon, 26 Dec 2011 16:19:14 +0000 From: Mark Brown To: Julia Lawall Cc: Samuel Ortiz , kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: devm_kfree Message-ID: <20111226161913.GJ8722@opensource.wolfsonmicro.com> References: <1324661974-17281-1-git-send-email-julia@diku.dk> <20111226120855.GB17760@sirena.org.uk> <20111226142354.GI8722@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Cookie: You are fairminded, just and loving. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 26, 2011 at 05:17:26PM +0100, Julia Lawall wrote: > And I guess that eg using kfree to free something allocated using > devm_kzalloc would be completely wrong, leading to a dangling > pointer? I'd expect that matching kfree() with devm_kzalloc() would lead to an attempt to double free whenever the devm_ mechanism kicks in.