From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Gavin Shan <shangw@linux.vnet.ibm.com>,
linux-mm@kvack.org, mhocko@suse.cz, rientjes@google.com,
hannes@cmpxchg.org, akpm@linux-foundation.org
Subject: Re: [PATCH v2 2/3] mm/sparse: fix possible memory leak
Date: Thu, 28 Jun 2012 14:03:30 +0800 [thread overview]
Message-ID: <20120628060330.GA26576@shangw> (raw)
In-Reply-To: <4FEB3C67.6070604@linux.vnet.ibm.com>
>> With CONFIG_SPARSEMEM_EXTREME, the root memory section descriptors
>> are allocated by slab or bootmem allocator. Also, the descriptors
>> might have been allocated and initialized during the hotplug path.
>> However, the memory chunk allocated in current implementation wouldn't
>> be put into the available pool if that has been allocated. The situation
>> will lead to memory leak.
>
>I've read this changelog about ten times and I'm still not really clear
>what the bug is here.
>
yep, I need improve my written English definitely :-)
>--
>
>sparse_index_init() is designed to be safe if two copies of it race. It
>uses "index_init_lock" to ensure that, even in the case of a race, only
>one CPU will manage to do:
>
> mem_section[root] = section;
>
>However, in the case where two copies of sparse_index_init() _do_ race,
>the one that loses the race will leak the "section" that
>sparse_index_alloc() allocated for it. This patch fixes that leak.
>
>--
Thank you very much, Dave. Let me merge your changelog into next version.
>
>Technically, I'm not sure that we can race during the time when we'd be
>using bootmem. I think we do all those initializations single-threaded
>at the moment, and we'd finish them before we turn the slab on. So,
>technically, we probably don't need the bootmem stuff in
>sparse_index_free(). But, I guess it doesn't hurt, and it's fine for
>completeness.
>
>Gavin, have you actually tested this in some way? It looks OK to me,
>but I worry that you've just added a block of code that's exceedingly
>unlikely to get run.
I didn't test this and I just catch the point while reading the source
code. By the way, I would like to know the popular utilities used for
memory testing. If you can share some information regarding that, that
would be great.
- memory related benchmark testing utility.
- some documents on Linux memory testing.
Thanks,
Gavin
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-06-28 6:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 16:36 [PATCH v2 1/3] mm/sparse: optimize sparse_index_alloc Gavin Shan
2012-06-27 16:36 ` [PATCH v2 2/3] mm/sparse: fix possible memory leak Gavin Shan
2012-06-27 17:01 ` Dave Hansen
2012-06-28 6:03 ` Gavin Shan [this message]
2012-06-28 14:54 ` Dave Hansen
2012-07-01 13:26 ` Gavin Shan
2012-06-27 22:07 ` David Rientjes
2012-06-28 6:16 ` Gavin Shan
2012-06-28 21:34 ` David Rientjes
2012-07-01 13:41 ` Gavin Shan
2012-06-28 12:57 ` Michal Hocko
2012-06-29 1:22 ` Gavin Shan
2012-06-27 16:36 ` [PATCH v2 3/3] mm/sparse: more check on mem_section number Gavin Shan
2012-06-27 22:06 ` David Rientjes
2012-06-27 22:14 ` Dave Hansen
2012-06-28 6:18 ` Gavin Shan
2012-06-27 22:10 ` [PATCH v2 1/3] mm/sparse: optimize sparse_index_alloc David Rientjes
2012-06-28 12:52 ` Michal Hocko
2012-06-29 1:20 ` Gavin Shan
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=20120628060330.GA26576@shangw \
--to=shangw@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.