From: Catalin Marinas <catalin.marinas@arm.com>
To: Anbu Manikandan <canbumanikandan@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Kmemleak feature
Date: Thu, 10 May 2012 18:21:16 +0100 [thread overview]
Message-ID: <20120510172116.GB20860@arm.com> (raw)
In-Reply-To: <CAAGB47NxugPZbV2ma-G7Aok5Xky=6AuyBGtis9U3hzNw8LDT0w@mail.gmail.com>
On Thu, May 10, 2012 at 05:42:35PM +0100, Anbu Manikandan wrote:
> As suggested by you, I have executed Kmemleak on 2.6.35-kernel and 3.0-RT
> kernel.
> I have noticed that Kmemleak behavior is little different between 2.6.35 and
> 3.0-RT kernel for vmalloc allocation memory leak. There is no entry for vmalloc
> allocation memory leak in 3.0-RT kernel.
...
> I tried modifying min_count value for vmalloc allocation from "3" to "4" as
> below in 3.0-RT kernel:
I can reproduce the missing vmalloc report on a non-rt 3.4-rc3 kernel as
well, so something must have changed in the vmalloc code in the past
months. A suspecting commit is f5252e00 but I need to investigate
whether a third reference to the vmalloc'ed pointer is stored in the
generic code somewhere before we decide to bump the min_count to 4.
--
Catalin
prev parent reply other threads:[~2012-05-10 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAGB47OajENL-g-CvdAgp1k2XKU4dOWbHz=mDy79mPOvi-eEmQ@mail.gmail.com>
[not found] ` <CAAGB47PiZ0cveWvObEjS8OPB++M3s1dENybnjoxyhQ8K_T4SpA@mail.gmail.com>
[not found] ` <CAAGB47PmB8o=mrnSoU1jYt_ecjH2WBLEzGRFqZWhWZXWQkTHaA@mail.gmail.com>
[not found] ` <CAAGB47PpTx9-eFz6ppbCYshA5yp293Tm1X-cAaBkZ+xX05_UUg@mail.gmail.com>
[not found] ` <CAAGB47N3oPkK1WhwzB7q4_6rvzKbnx3Ugwdr+aUuwTqiNX2oog@mail.gmail.com>
2012-05-09 6:27 ` Pekka Enberg
2012-05-09 8:22 ` Catalin Marinas
[not found] ` <CAAGB47NxugPZbV2ma-G7Aok5Xky=6AuyBGtis9U3hzNw8LDT0w@mail.gmail.com>
2012-05-10 17:21 ` Catalin Marinas [this message]
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=20120510172116.GB20860@arm.com \
--to=catalin.marinas@arm.com \
--cc=canbumanikandan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@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®