summaryrefslogtreecommitdiffstats
path: root/include/linux/misc_cgroup.h
diff options
context:
space:
mode:
authorChunguang Xu <brookxu@tencent.com>2021-09-17 20:44:15 +0800
committerTejun Heo <tj@kernel.org>2021-09-20 07:35:38 -1000
commitb03357528fd9516600ff358ab5d4b887b8cb80e8 (patch)
tree037b3e4f1b5a4afa466ee0f2f349b4b9a338a52f /include/linux/misc_cgroup.h
parentf279294b329363eb6ada568e494d609ef78e3e8e (diff)
downloadlinux-stable-b03357528fd9516600ff358ab5d4b887b8cb80e8.tar.gz
linux-stable-b03357528fd9516600ff358ab5d4b887b8cb80e8.tar.bz2
linux-stable-b03357528fd9516600ff358ab5d4b887b8cb80e8.zip
misc_cgroup: remove error log to avoid log flood
In scenarios where containers are frequently created and deleted, a large number of error logs maybe generated. The logs only show which node is about to go over the max limit, not the node which resource request failed. As misc.events has provided relevant information, maybe we can remove this log. Signed-off-by: Chunguang Xu <brookxu@tencent.com> Reviewed-by: Michal Koutný <mkoutny@suse.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'include/linux/misc_cgroup.h')
-rw-r--r--include/linux/misc_cgroup.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/misc_cgroup.h b/include/linux/misc_cgroup.h
index 091f2d2a1aec..c238207d1615 100644
--- a/include/linux/misc_cgroup.h
+++ b/include/linux/misc_cgroup.h
@@ -37,7 +37,6 @@ struct misc_res {
unsigned long max;
atomic_long_t usage;
atomic_long_t events;
- bool failed;
};
/**