[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <398315856.259038.1487972318815@email.1und1.de>
Date: Fri, 24 Feb 2017 22:38:38 +0100 (CET)
From: Stefan Wahren <stefan.wahren@...e.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: lee@...nel.org, rjui@...adcom.com, linux-media@...r.kernel.org,
eric@...olt.net, kernel-janitors@...r.kernel.org, arnd@...db.de,
linux-arm-kernel@...ts.infradead.org, mchehab@...nel.org,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
sbranden@...adcom.com, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com, devel@...verdev.osuosl.org,
swarren@...dotorg.org, f.fainelli@...il.com,
linux-rpi-kernel@...ts.infradead.org
Subject: Re: [PATCH] staging: bcm2835: Fix a memory leak in error handling
path
> Dan Carpenter <dan.carpenter@...cle.com> hat am 24. Februar 2017 um 20:57 geschrieben:
>
>
> On Fri, Feb 24, 2017 at 01:37:30PM +0100, Stefan Wahren wrote:
> > Hi Christophe,
> >
> > Am 19.02.2017 um 11:34 schrieb Christophe JAILLET:
> > >If 'kzalloc()' fails, we should release resources allocated so far, just as
> > >done in all other cases in this function.
> > >
> > >Signed-off-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>
> > >---
> > >Not sure that the error handling path is correct.
> > >Is 'gdev[0]' freed? Should it be?
> >
>
> Yes, but I already sent a patch to fix this and your leak as well and
> Greg merged it.
My leak? I'm confused.
Powered by blists - more mailing lists