From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.19.201]:43397 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758475AbaGOR3M (ORCPT ); Tue, 15 Jul 2014 13:29:12 -0400 Message-ID: <53C5656F.9030200@kernel.org> Date: Tue, 15 Jul 2014 18:31:27 +0100 From: Jonathan Cameron MIME-Version: 1.0 To: Himangi Saraogi , Greg Kroah-Hartman , linux-iio@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org CC: Julia Lawall , Lars-Peter Clausen Subject: Re: question regarding drivers/staging/iio/adc/ad7280a.c References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org On 14/07/14 21:31, Himangi Saraogi wrote: > Hi, > > The code seems to have a memory leak. The function ad7280_attr_init > calls kasprintf a number of times, which calls kmalloc (or more > precisely kmalloc_track_caller), but this data does not ever seem to > be freed. I propose to introduce a devm_ version of kasprintf, which > will be useful for other files also. I am not very sure that will it > be useful to introduce a bunch of kfrees, just to remove the memory > leaks immediately, but I think it would be safer just to devm > everything, so then one is sure that everything is freed as it should > be, in the right order. > The question here is whether such a memory leak squashing would be worth applying to stable. Personally I'd go with no. In which case feel free to fix it via the introduction of a devm version. Jonathan > Thanks > Himangi