From: Roland Eggner <edvx1@systemanalysen.net>
To: linux-kernel@vger.kernel.org
Subject: [kmemleak report 0/2] kernel 3.1.6, x86_64
Date: Sun, 15 Jan 2012 23:29:33 +0100 [thread overview]
Message-ID: <20120115222932.GA24330@mobil.systemanalysen.net> (raw)
It looks like memory leaks are “eating” 1G+ after only 1 week uptime … that's
not nice.
I get 2 types of kmemleak backtraces, most likely 2 different issues, thus
2 seperate mails will follow as reply to this mail.
--
Roland Eggner
next reply other threads:[~2012-01-15 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 22:29 Roland Eggner [this message]
2012-01-15 22:37 ` [kmemleak report 1/2] kernel 3.1.6, x86_64: mm, xfs ?, vfs ? Roland Eggner
2012-01-20 0:08 ` Roland Eggner
2012-02-06 6:11 ` Dave Chinner
2012-01-15 22:38 ` [kmemleak report 2/2] kernel 3.1.6, x86_64: pm, acpi-cpufreq ? Roland Eggner
2012-01-17 16:53 ` [kmemleak report 0/2] kernel 3.1.6, x86_64 Catalin Marinas
2012-01-19 13:21 ` Roland Eggner
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=20120115222932.GA24330@mobil.systemanalysen.net \
--to=edvx1@systemanalysen.net \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®