From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darren Jenkins Subject: Re: [PATCH] drivers/net/wimax/i2400m/fw.c fix possible double free Date: Thu, 18 Mar 2010 19:46:48 +1100 Message-ID: <1268902008.10536.41.camel@ICE-BOX> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "Kao, Cindy H" , "wimax@linuxwimax.org" , "netdev@vger.kernel.org" , "kernel-janitors@vger.kernel.org" , Linux Kernel Mailing List , linux-wimax , David Miller To: Inaky Perez-Gonzalez Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: wimax-bounces@linuxwimax.org Errors-To: wimax-bounces@linuxwimax.org List-Id: netdev.vger.kernel.org On Thu, Mar 18, 2010 at 9:10 AM, Inaky Perez-Gonzalez wrote: > If krealloc() fails to aallocate a new pointer, the old block is > unmodified, so by doing this you are leaking a buffer allocation. It seems you are right. So now understanding correctly how krealloc() works I can see that the double kfree() can only actually happen if the el_size parameter to i2400m_zrealloc_2x() is zero, and it isn't at the two call sites. So this was a false positive and I am sorry for the noise. Darren J.