[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A61CE59.3030905@fisher-privat.net>
Date: Sat, 18 Jul 2009 15:30:01 +0200
From: Alexey Fisher <bug-track@...her-privat.net>
To: Ingo Molnar <mingo@...e.hu>
CC: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
Catalin Marinas <catalin.marinas@....com>,
Pekka Enberg <penberg@...helsinki.fi>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sam Ravnborg <sam@...nborg.org>, linux-ext4@...r.kernel.org
Subject: Re: ext4 memory leak (was Re: [PATCH] x86: _edata should include
all .data.* sections on X86_64)
Ingo Molnar schrieb:
> * Alexey Fisher <bug-track@...her-privat.net> wrote:
>
>> This patch work for me.
>
> nice. Any leftovers that might be false positives and need
> annotation?
>
> We learned this with lockdep: the moment a typical x86 distro bootup
> is 'warnings free', utility of the debugging facility increases
> dramatically: people can standardize on 'kmemleak should never
> produce warnings' workflows and distros can also start feeding
> kmemleak reports into kerneloops.org or so.
>
> So the general direction kmemleak is moving into is really
> encouraging.
>
> Ingo
suddenly my kernel is not warning free... i have still warning about
acpi_init, cpufreg, intel_gem and inoitfy on my PC and about firmware
loader on my laptop. So i think there is still some job to do. I will
report this warnings soon.
--
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