linux-toradex.git/mm/percpu.c, branch v3.10.61

Revert "percpu: free percpu allocation info for uniprocessor system"

2014-11-14T16:47:53+00:00

commit bb2e226b3bef596dd56be97df655d857b4603923 upstream.

This reverts commit 3189eddbcafc ("percpu: free percpu allocation info for
uniprocessor system").

The commit causes a hang with a crisv32 image. This may be an architecture
problem, but at least for now the revert is necessary to be able to boot a
crisv32 image.

Cc: Tejun Heo 
Cc: Honggang Li 
Signed-off-by: Guenter Roeck 
Signed-off-by: Tejun Heo 
Fixes: 3189eddbcafc ("percpu: free percpu allocation info for uniprocessor system")
Signed-off-by: Greg Kroah-Hartman

percpu: free percpu allocation info for uniprocessor system

2014-10-05T21:54:13+00:00

commit 3189eddbcafcc4d827f7f19facbeddec4424eba8 upstream.

Currently, only SMP system free the percpu allocation info.
Uniprocessor system should free it too. For example, one x86 UML
virtual machine with 256MB memory, UML kernel wastes one page memory.

Signed-off-by: Honggang Li 
Signed-off-by: Tejun Heo 
Signed-off-by: Greg Kroah-Hartman

percpu: make pcpu_alloc_chunk() use pcpu_mem_free() instead of kfree()

2014-06-07T20:25:37+00:00

commit 5a838c3b60e3a36ade764cf7751b8f17d7c9c2da upstream.

pcpu_chunk_struct_size = sizeof(struct pcpu_chunk) +
	BITS_TO_LONGS(pcpu_unit_pages) * sizeof(unsigned long)

It hardly could be ever bigger than PAGE_SIZE even for large-scale machine,
but for consistency with its couterpart pcpu_mem_zalloc(),
use pcpu_mem_free() instead.

Commit b4916cb17c26 ("percpu: make pcpu_free_chunk() use
pcpu_mem_free() instead of kfree()") addressed this problem, but
missed this one.

tj: commit message updated

Signed-off-by: Jianyu Zhan 
Signed-off-by: Tejun Heo 
Fixes: 099a19d91ca4 ("percpu: allow limited allocation before slab is online)
Signed-off-by: Greg Kroah-Hartman

mm, percpu: Make sure percpu_alloc early parameter has an argument

2012-12-02T14:23:04+00:00

Otherwise we are getting a nil dereference if percpu_alloc kernel boot
argument is specified without value.

 | [    0.000000] BUG: unable to handle kernel NULL pointer dereference at           (null)
 | [    0.000000] IP: [] strcmp+0x10/0x30

Signed-off-by: Cyrill Gorcunov 
Signed-off-by: Tejun Heo

percpu: make pcpu_free_chunk() use pcpu_mem_free() instead of kfree()

2012-10-29T15:49:47+00:00

commit 099a19d9('allow limited allocation before slab is online') made
pcpu_alloc_chunk() use pcpu_mem_zalloc() but forgot to update
pcpu_free_chunk() accordingly.  This doesn't cause any immediate
problema, but fix it for consistency.

tj: commit message updated

Signed-off-by: Joonsoo Kim 
Cc: Christoph Lameter 
Signed-off-by: Tejun Heo

sections: fix section conflicts in mm/percpu.c

2012-10-05T18:04:44+00:00

Signed-off-by: Andi Kleen 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kmemleak: Fix the kmemleak tracking of the percpu areas with !SMP

2012-05-09T17:13:29+00:00

Kmemleak tracks the percpu allocations via a specific API and the
originally allocated areas must be removed from kmemleak (via
kmemleak_free). The code was already doing this for SMP systems.

Reported-by: Sami Liedes 
Cc: Tejun Heo 
Cc: Christoph Lameter 
Signed-off-by: Catalin Marinas 
Signed-off-by: Tejun Heo

percpu: pcpu_embed_first_chunk() should free unused parts after all allocs are complete

2012-05-09T17:08:16+00:00

pcpu_embed_first_chunk() allocates memory for each node, copies percpu
data and frees unused portions of it before proceeding to the next
group.  This assumes that allocations for different nodes doesn't
overlap; however, depending on memory topology, the bootmem allocator
may end up allocating memory from a different node than the requested
one which may overlap with the portion freed from one of the previous
percpu areas.  This leads to percpu groups for different nodes
overlapping which is a serious bug.

This patch separates out copy & partial free from the allocation loop
such that all allocations are complete before partial frees happen.

This also fixes overlapping frees which could happen on allocation
failure path - out_free_areas path frees whole groups but the groups
could have portions freed at that point.

Signed-off-by: Tejun Heo 
Cc: stable@vger.kernel.org
Reported-by: "Pavel V. Panteleev" 
Tested-by: "Pavel V. Panteleev" 
LKML-Reference:

percpu: use KERN_CONT in pcpu_dump_alloc_info()

2012-03-29T16:45:58+00:00

pcpu_dump_alloc_info() was printing continued lines without KERN_CONT.
Use it.

Signed-off-by: Tejun Heo 
Reported-by: Kay Sievers

Merge tag 'kmemleak' of git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux

2012-01-15T02:11:11+00:00

Kmemleak patches

Main features:
- Handle percpu memory allocations (only scanning them, not actually
  reporting).
- Memory hotplug support.

Usability improvements:
- Show the origin of early allocations.
- Report previously found leaks even if kmemleak has been disabled by
  some error.

* tag 'kmemleak' of git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux:
  kmemleak: Add support for memory hotplug
  kmemleak: Handle percpu memory allocation
  kmemleak: Report previously found leaks even after an error
  kmemleak: When the early log buffer is exceeded, report the actual number
  kmemleak: Show where early_log issues come from