The patch titled
Subject: memcg: revise the position of threshold index while unregistering event
has been removed from the -mm tree. Its filename was
memcg-revise-the-position-of-threshold-index-while-unregistering-event.patch
This patch was dropped because it was folded into memcg-make-threshold-index-in-the-right-position.patch
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
From: Sha Zhengju <handai.szj@xxxxxxxxxx>
Subject: memcg: revise the position of threshold index while unregistering event
Index current_threshold should point to threshold just below or equal to
usage. See below: http://www.spinics.net/lists/cgroups/msg00844.html
Signed-off-by: Sha Zhengju <handai.szj@xxxxxxxxxx>
Reviewed-by: Kirill A. Shutemov <kirill@xxxxxxxxxxxxx>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
Cc: Johannes Weiner <hannes@xxxxxxxxxxx>
Cc: Michal Hocko <mhocko@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/memcontrol.c~memcg-revise-the-position-of-threshold-index-while-unregistering-event mm/memcontrol.c
--- a/mm/memcontrol.c~memcg-revise-the-position-of-threshold-index-while-unregistering-event
+++ a/mm/memcontrol.c
@@ -4695,7 +4695,7 @@ static void mem_cgroup_usage_unregister_
continue;
new->entries[j] = thresholds->primary->entries[i];
- if (new->entries[j].threshold < usage) {
+ if (new->entries[j].threshold <= usage) {
/*
* new->current_threshold will not be used
* until rcu_assign_pointer(), so it's safe to increment
_
Patches currently in -mm which might be from handai.szj@xxxxxxxxxx are
memcg-make-threshold-index-in-the-right-position.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
