mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Alexey Fisher <bug-track@fisher-privat.net>,
	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>,
	linux-ext4@vger.kernel.org
Subject: Re: ext4 memory leak (was Re: [PATCH] x86: _edata should include all .data.* sections on X86_64)
Date: Wed, 15 Jul 2009 11:33:15 +0100	[thread overview]
Message-ID: <1247653995.10407.25.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20090715080336.GA4823@skywalker>

On Wed, 2009-07-15 at 13:33 +0530, Aneesh Kumar K.V wrote:
> Can you try this patch ?
[...]
>     ext4: Memory leak fix ext4_group_info allocation.
>     
>     commit 5f21b0e642d7bf6fe4434c9ba12bc9cb96b17cf7  was done to
>     reallocate groupinfo struct during resize properly. That goal
>     was to allocate new groupinfo struct when we are adding new block
>     groups during resize. Calling ext4_mb_add_group_info in the
>     mballoc initialization code path resulted in we reallocating
>     the group info struct . Fix this by not separately allocating
>     group info in the mballoc init path and always depend on
>     ext4_mb_add_group_info to allocate group info struct.
>     
>     The earlier code also had a bug that we allocated less number of
>     group info struct for the last meta group. But on resize we
>     expected that we had EXT4_DESC_PER_BLOCK group info struct for
>     each meta group.
>     
>     Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>

The kmemleak report disappeared.

Tested-by: Catalin Marinas <catalin.marinas@arm.com>

BTW, there are a few compiler warnings about unused variables with this
patch.

-- 
Catalin


  parent reply	other threads:[~2009-07-15 10:33 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
2009-07-18 22:44                         ` Catalin Marinas
2009-07-18 22:33                       ` Catalin Marinas
2009-07-15 10:33                   ` Catalin Marinas [this message]
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=1247653995.10407.25.camel@pc1117.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=bug-track@fisher-privat.net \
    --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

all inboxes | Powered by JetHome®