Re: Possible memory leak in net/wireless/scan.c
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Date: Tue, 07 Jul 2009 23:47:21 +0200
On Tue, 2009-07-07 at 22:29 +0100, Catalin Marinas wrote:
if (found) {
- kref_get(&found->ref);
found->pub.beacon_interval = res->pub.beacon_interval;
found->pub.tsf = res->pub.tsf;
found->pub.signal = res->pub.signal;
I'll try this later today to see if it fixes the leak. If that's not
correct, I'll post more information about the content of the reported
object (in general, it shouldn't be on any valid list or rb tree since
kmemleak can't find it).
I have already sent that exact patch.
OK. I can now confirm that it fixes the memory leak.
Great, thanks for checking.
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- Possible memory leak in net/wireless/scan.c
- From: Catalin Marinas
- Re: Possible memory leak in net/wireless/scan.c
- From: Johannes Berg
- Re: Possible memory leak in net/wireless/scan.c
- From: Catalin Marinas
- Possible memory leak in net/wireless/scan.c
- Prev by Date: Re: [PATCH -tip -v10 7/7] tracing: add kprobe-based event tracer
- Next by Date: Re: Possible memory leak in request_firmware()
- Previous by thread: Re: Possible memory leak in net/wireless/scan.c
- Next by thread: Re: Possible memory leak in net/wireless/scan.c
- Index(es):
Relevant Pages
|
