From: Alexey Fisher <bug-track@fisher-privat.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-ext4@vger.kernel.org
Subject: Re: ext4 memory leak (was Re: [PATCH] x86: _edata should include all .data.* sections on X86_64)
Date: Sat, 18 Jul 2009 15:30:01 +0200 [thread overview]
Message-ID: <4A61CE59.3030905@fisher-privat.net> (raw)
In-Reply-To: <20090718115556.GA31007@elte.hu>
Ingo Molnar schrieb:
> * Alexey Fisher <bug-track@fisher-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.
next prev parent reply other threads:[~2009-07-18 13:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 6:08 60 memory leaks.. or is it some thing wrong with kmemleak? Alexey Fisher
2009-07-14 7:19 ` Pekka Enberg
2009-07-14 8:28 ` Alexey Fisher
2009-07-14 9:39 ` Catalin Marinas
2009-07-14 9:52 ` [PATCH] x86: _edata should include all .data.* sections on X86_64 Catalin Marinas
2009-07-14 10:13 ` Alexey Fisher
2009-07-14 10:31 ` Catalin Marinas
2009-07-14 10:37 ` Alexey Fisher
2009-07-14 12:26 ` ext4 memory leak (was Re: [PATCH] x86: _edata should include all .data.* sections on X86_64) Catalin Marinas
2009-07-15 8:03 ` Aneesh Kumar K.V
2009-07-15 8:54 ` Alexey Fisher
2009-07-18 11:55 ` Ingo Molnar
2009-07-18 13:30 ` Alexey Fisher [this message]
2009-07-18 22:44 ` Catalin Marinas
2009-07-18 22:33 ` Catalin Marinas
2009-07-15 10:33 ` Catalin Marinas
2009-07-14 12:42 ` [PATCH] x86: _edata should include all .data.* sections on X86_64 Catalin Marinas
2009-07-16 20:23 ` Sam Ravnborg
2009-07-18 12:06 ` [tip:x86/urgent] x86: Include all of .data.* sections in _edata on 64-bit tip-bot for Catalin Marinas
2009-07-18 20:29 ` [kmemleak] 60 wornings on sysfs_new_dirent+0x10c Alexey Fisher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A61CE59.3030905@fisher-privat.net \
--to=bug-track@fisher-privat.net \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox