mm/memcg: fix obsolete function name in mem_cgroup_protection()
authorMiaohe Lin <linmiaohe@huawei.com>
Thu, 27 Jul 2023 11:59:34 +0000 (19:59 +0800)
committerAndrew Morton <akpm@linux-foundation.org>
Mon, 21 Aug 2023 20:37:28 +0000 (13:37 -0700)
Commit 45c7f7e1ef17 ("mm, memcg: decouple e{low,min} state mutations from
protection checks") changed the function name but not the corresponding
comment.

Link: https://lkml.kernel.org/r/20230727115934.657787-1-linmiaohe@huawei.com
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Roman Gushchin <roman.gushchin@linux.dev>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Shakeel Butt <shakeelb@google.com>
Cc: Muchun Song <songmuchun@bytedance.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
include/linux/memcontrol.h

index 058fb748e128440718cc83d7b24afa5be6cdaad0..419e001a02e401b32c110238c3c83b93cd693e25 100644 (file)
@@ -582,7 +582,7 @@ static inline void mem_cgroup_protection(struct mem_cgroup *root,
        /*
         * There is no reclaim protection applied to a targeted reclaim.
         * We are special casing this specific case here because
-        * mem_cgroup_protected calculation is not robust enough to keep
+        * mem_cgroup_calculate_protection is not robust enough to keep
         * the protection invariant for calculated effective values for
         * parallel reclaimers with different reclaim target. This is
         * especially a problem for tail memcgs (as they have pages on LRU)