xavi/android_kernel_m2note/mm/slab.h, branch ng-7.1.2

panic on kmem_cache_free with the wrong cache

2018-05-16T11:24:56+00:00

always perform cache_from_obj sanity checks

2018-05-16T11:24:41+00:00

real slab_equal_or_root check for !MEMCG_KMEM

2018-05-16T11:24:27+00:00

add missing cache_from_obj !PageSlab check

2018-05-16T11:24:14+00:00

Taken from PaX.

misc: replace FUNCTION by function

2017-09-23T01:10:48+00:00

result of : git grep -l '__FUNCTION__' | xargs sed -i 's/__FUNCTION__/__func__/g'

mm/slab: Give s_next and s_stop slab-specific names

2016-09-28T13:14:26+00:00

Give s_next and s_stop slab-specific names instead of exporting "s_next" and "s_stop". Signed-off-by: Wanpeng Li Signed-off-by: Pekka Enberg Signed-off-by: W4TCH0UT

mm/slab: Sharing s_next and s_stop between slab and slub

2016-09-28T13:14:24+00:00

This patch shares s_next and s_stop between slab and slub. Acked-by: Christoph Lameter Signed-off-by: Wanpeng Li Signed-off-by: Pekka Enberg Signed-off-by: W4TCH0UT

memcg, slab: never try to merge memcg caches

2016-09-28T13:14:03+00:00

When a kmem cache is created (kmem_cache_create_memcg()), we first try to find a compatible cache that already exists and can handle requests from the new cache, i.e. has the same object size, alignment, ctor, etc. If there is such a cache, we do not create any new caches, instead we simply increment the refcount of the cache found and return it. Currently we do this procedure not only when creating root caches, but also for memcg caches. However, there is no point in that, because, as every memcg cache has exactly the same parameters as its parent and cache merging cannot be turned off in runtime (only on boot by passing "slub_nomerge"), the root caches of any two potentially mergeable memcg caches should be merged already, i.e. it must be the same root cache, and therefore we couldn't even get to the memcg cache creation, because it already exists. The only exception is boot caches - they are explicitly forbidden to be merged by setting their refcount to -1. There are currently only two of them - kmem_cache and kmem_cache_node, which are used in slab internals (I do not count kmalloc caches as their refcount is set to 1 immediately after creation). Since they are prevented from merging preliminary I guess we should avoid to merge their children too. So let's remove the useless code responsible for merging memcg caches. Signed-off-by: Vladimir Davydov Cc: Michal Hocko Cc: Johannes Weiner Cc: David Rientjes Cc: Pekka Enberg Cc: Glauber Costa Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds Signed-off-by: W4TCH0UT Conflicts: mm/slab_common.c Signed-off-by: W4TCH0UT

memcg, kmem: rename cache_from_memcg to cache_from_memcg_idx

2016-09-28T13:12:54+00:00

We can't see the relationship with memcg from the parameters, so the name with memcg_idx would be more reasonable. Signed-off-by: Qiang Huang Reviewed-by: Pekka Enberg Acked-by: David Rientjes Cc: Johannes Weiner Cc: Michal Hocko Cc: Glauber Costa Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds Signed-off-by: W4TCH0UT

first commit

2016-08-15T02:19:42+00:00