[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1268902008.10536.41.camel@ICE-BOX>
Date: Thu, 18 Mar 2010 19:46:48 +1100
From: Darren Jenkins <darrenrjenkins@...il.com>
To: Inaky Perez-Gonzalez <inaky.perez-gonzalez@...el.com>
Cc: David Miller <davem@...emloft.net>,
linux-wimax <linux-wimax@...el.com>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"Kao, Cindy H" <cindy.h.kao@...el.com>,
"Brandewie, Dirk J" <dirk.j.brandewie@...el.com>,
"wimax@...uxwimax.org" <wimax@...uxwimax.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drivers/net/wimax/i2400m/fw.c fix possible double free
On Thu, Mar 18, 2010 at 9:10 AM, Inaky Perez-Gonzalez
<inaky.perez-gonzalez@...el.com> 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.
--
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/
Powered by blists - more mailing lists