[PATCH] rt2x00: Don't leak mem in error path of rt2x00lib_request_firmware() · Jesper Juhl <hidden> · 2011-01-10
Re: [PATCH] rt2x00: Don't leak mem in error path of rt2x00lib_request_firmware() · Ivo Van Doorn <hidden> · 2011-01-11
Re: [PATCH] rt2x00: Don't leak mem in error path of rt2x00lib_request_firmware() · Pekka Enberg <penberg@kernel.org> · 2011-01-11

Re: [PATCH] rt2x00: Don't leak mem in error path of rt2x00lib_request_firmware()

Pekka Enberg · 2011-01-11T19:33:13+0200

On Tue, Jan 11, 2011 at 7:30 PM, Ivo Van Doorn wrote: > Hi, > >> We need to release_firmware() in order not to leak memory. >> >> Signed-off-by: Jesper Juhl > > I can assume that release_firmware() checks if 'fw' is null? Yes, it does. > If so: > > Acked-by: Ivo van Doorn Acked-by: Pekka Enberg

flat view

From: Pekka Enberg <penberg@kernel.org>
Date: 2011-01-11 17:33:17
Also in: lkml, netdev

On Tue, Jan 11, 2011 at 7:30 PM, Ivo Van Doorn [off-list ref] wrote:

Hi,

quoted

We need to release_firmware() in order not to leak memory.

Signed-off-by: Jesper Juhl <redacted>

I can assume that release_firmware() checks if 'fw' is null?

Yes, it does.

If so:

Acked-by: Ivo van Doorn <redacted>

Acked-by: Pekka Enberg <penberg@kernel.org>

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help