From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Gavin Shan <shangw@linux.vnet.ibm.com>,
linux-mm@kvack.org, dave@linux.vnet.ibm.com, rientjes@google.com,
hannes@cmpxchg.org, akpm@linux-foundation.org
Subject: Re: [PATCH v2 2/3] mm/sparse: fix possible memory leak
Date: Fri, 29 Jun 2012 09:22:12 +0800 [thread overview]
Message-ID: <20120629012212.GB10542@shangw> (raw)
In-Reply-To: <20120628125742.GC16042@tiehlicka.suse.cz>
On Thu, Jun 28, 2012 at 02:57:42PM +0200, Michal Hocko wrote:
>On Thu 28-06-12 00:36:07, Gavin Shan wrote:
>> 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.
>>
>> Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
>> Reviewed-by: Michal Hocko <mhocko@suse.cz>
>
>And again!
>To quote my answers to this patch in previous run:
>"
>I am not saying the bug is not real. It is just that the changelog
>doesn's say how the bug is hit, who is affected and when it has been
>introduced. These is essential for stable.
>"
>
>Does this sound like Reviewed-by? Hell no!
>
Ok. I won't do this again wrongly.
>This changelog btw. doesn't say this either!
>
Here's the changelog that Dave suggested. I just copy & paste it.
--
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.
--
Thanks,
Gavin
>> ---
>> mm/sparse.c | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/mm/sparse.c b/mm/sparse.c
>> index 781fa04..a803599 100644
>> --- a/mm/sparse.c
>> +++ b/mm/sparse.c
>> @@ -75,6 +75,22 @@ static struct mem_section noinline __init_refok *sparse_index_alloc(int nid)
>> return section;
>> }
>>
>> +static void noinline __init_refok sparse_index_free(struct mem_section *section,
>> + int nid)
>> +{
>> + unsigned long size = SECTIONS_PER_ROOT *
>> + sizeof(struct mem_section);
>> +
>> + if (!section)
>> + return;
>> +
>> + if (slab_is_available())
>> + kfree(section);
>> + else
>> + free_bootmem_node(NODE_DATA(nid),
>> + virt_to_phys(section), size);
>> +}
>> +
>> static int __meminit sparse_index_init(unsigned long section_nr, int nid)
>> {
>> static DEFINE_SPINLOCK(index_init_lock);
>> @@ -102,6 +118,9 @@ static int __meminit sparse_index_init(unsigned long section_nr, int nid)
>> mem_section[root] = section;
>> out:
>> spin_unlock(&index_init_lock);
>> + if (ret)
>> + sparse_index_free(section, nid);
>> +
>> return ret;
>> }
>> #else /* !SPARSEMEM_EXTREME */
>> --
>> 1.7.9.5
>>
>
>--
>Michal Hocko
>SUSE Labs
>SUSE LINUX s.r.o.
>Lihovarska 1060/12
>190 00 Praha 9
>Czech Republic
>
>--
>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>
>
--
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-29 1:23 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
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 [this message]
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=20120629012212.GB10542@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).