linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Daniel Baluta <dbaluta@ixiacom.com>
Cc: Maxin John <maxin.john@gmail.com>,
	naveen yadav <yad.naveen@gmail.com>,
	linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: kmemleak for MIPS
Date: Wed, 30 Mar 2011 12:38:05 +0100	[thread overview]
Message-ID: <1301485085.29074.61.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <AANLkTi=vcn5jHpk0O8XS9XJ8s5k-mCnzUwu70mFTx4=g@mail.gmail.com>

On Wed, 2011-03-30 at 12:24 +0100, Daniel Baluta wrote:
> We have:
> 
> > UDP hash table entries: 128 (order: 0, 4096 bytes)
> > CONFIG_BASE_SMALL=0
> 
> udp_table_init looks like:
> 
>         if (!CONFIG_BASE_SMALL)
>                 table->hash = alloc_large_system_hash(name, .. &table->mask);
>         /*
>          * Make sure hash table has the minimum size
>          */
> 
> Since CONFIG_BASE_SMALL is 0, we are allocating the hash using
> alloc_large_system
> Then:
>         if (CONFIG_BASE_SMALL || table->mask < UDP_HTABLE_SIZE_MIN - 1) {
>                 table->hash = kmalloc();
> 
> table->mask is 127, and UDP_HTABLE_SIZE_MIN is 256, so we are allocating again
> table->hash without freeing already allocated memory.

Indeed (on my ARM system the reported UDP hash table entries is 512, so
I don't get the memory leak).

> We could free table->hash, before allocating the memory with kmalloc.
> I don't fully understand the condition table->mask < UDP_HTABLE_SIZE_MIN - 1.

We don't have the equivalent of free_large_system_hash(). Reordering the
'if' blocks may be better.

-- 
Catalin


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-03-30 11:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 13:54 naveen yadav
2011-03-24  9:27 ` Daniel Baluta
2011-03-24  9:55   ` Catalin Marinas
2011-03-28 21:15     ` Maxin John
2011-03-29 10:40       ` Catalin Marinas
2011-03-29 11:38         ` Maxin John
2011-03-29 11:50           ` Catalin Marinas
2011-03-29 12:27             ` Maxin John
2011-03-29 19:36               ` Maxin John
2011-03-29 19:54                 ` Daniel Baluta
2011-03-30  9:15                 ` Catalin Marinas
2011-03-30  9:54                   ` Daniel Baluta
2011-03-30  9:58                     ` Catalin Marinas
2011-03-30 11:03                     ` Maxin John
2011-03-30 11:24                       ` Daniel Baluta
2011-03-30 11:38                         ` Catalin Marinas [this message]
2011-03-30 12:17                           ` Maxin John
2011-03-30 12:27                             ` Eric Dumazet
2011-03-30 12:40                               ` Maxin John
2011-03-30 12:52                               ` Daniel Baluta
2011-03-30 13:17                                 ` Maxin John
2011-03-30 13:27                                   ` Eric Dumazet
2011-03-30 14:07                                     ` Maxin John
2011-03-30 14:07                                     ` Catalin Marinas
2011-03-30 12:22                         ` Eric Dumazet
2011-03-30 10:08                   ` Maxin John
2011-03-30 14:28                 ` Ralf Baechle
2011-03-30 14:21         ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2009-11-02 17:07 Kmemleak for mips Luis R. Rodriguez
2009-11-03  9:23 ` Catalin Marinas

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=1301485085.29074.61.camel@e102109-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=dbaluta@ixiacom.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mm@kvack.org \
    --cc=maxin.john@gmail.com \
    --cc=yad.naveen@gmail.com \
    /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