diff options
author | Gavin Shan <shangw@linux.vnet.ibm.com> | 2012-05-30 02:06:50 +0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-05-30 03:22:24 +0400 |
commit | 181eb39425f2b9275afcb015eaa547d11f71a02f (patch) | |
tree | 0ce0f09b5a86931e580a0a6b88e546831c7318ed /Documentation/cgroups/memory.txt | |
parent | 4e2f07750d9a94e8f23e86408df5ab95be88bf11 (diff) | |
download | linux-181eb39425f2b9275afcb015eaa547d11f71a02f.tar.xz |
mm/memblock: fix memory leak on extending regions
The overall memblock has been organized into the memory regions and
reserved regions. Initially, the memory regions and reserved regions are
stored in the predetermined arrays of "struct memblock _region". It's
possible for the arrays to be enlarged when we have newly added regions,
but no free space left there. The policy here is to create double-sized
array either by slab allocator or memblock allocator. Unfortunately, we
didn't free the old array, which might be allocated through slab allocator
before. That would cause memory leak.
The patch introduces 2 variables to trace where (slab or memblock) the
memory and reserved regions come from. The memory for the memory or
reserved regions will be deallocated by kfree() if that was allocated by
slab allocator. Thus to fix the memory leak issue.
Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/cgroups/memory.txt')
0 files changed, 0 insertions, 0 deletions