From: Catalin Marinas <catalin.marinas@arm.com>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: 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>, Ingo Molnar <mingo@elte.hu>,
x86@kernel.org
Subject: Re: [PATCH] x86: _edata should include all .data.* sections on X86_64
Date: Tue, 14 Jul 2009 11:31:39 +0100 [thread overview]
Message-ID: <1247567499.28240.48.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <4A5C5A59.5080304@fisher-privat.net>
On Tue, 2009-07-14 at 12:13 +0200, Alexey Fisher wrote:
> With this patch i have only 25 reports....
> but i still have a lot of ext4 and some other reports.
Apart from ext4, what are the other reports?
Thanks.
--
Catalin
next prev parent reply other threads:[~2009-07-14 10:32 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 [this message]
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
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=1247567499.28240.48.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=bug-track@fisher-privat.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=sam@ravnborg.org \
--cc=x86@kernel.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
Powered by JetHome