Re: [-mm patch] Show memcg information during OOM (v3)

From: Balbir Singh
Date: Fri Feb 06 2009 - 02:01:34 EST


* Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> [2009-02-05 13:55:54]:

>
> ping?
>

Andrew,

This patch fixes issues reported with the OOM printing patches.

From: Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx>

1. It reduces the static buffers from 2 to 1
2. It fixes comments that incorrectly indicate that the buffer is on stack

This patch fails checkpatch.pl, due to split of the printk message.
I could not find an easy way to fix it.

Signed-off-by: Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx>
---

mm/memcontrol.c | 23 +++++++++++++++--------
1 files changed, 15 insertions(+), 8 deletions(-)


diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 839258e..9180702 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -736,22 +736,23 @@ void mem_cgroup_print_oom_info(struct mem_cgroup *memcg, struct task_struct *p)
struct cgroup *task_cgrp;
struct cgroup *mem_cgrp;
/*
- * Need a buffer on stack, can't rely on allocations. The code relies
+ * Need a buffer in BSS, can't rely on allocations. The code relies
* on the assumption that OOM is serialized for memory controller.
* If this assumption is broken, revisit this code.
*/
- static char task_memcg_name[PATH_MAX];
static char memcg_name[PATH_MAX];
int ret;

if (!memcg)
return;

- mem_cgrp = memcg->css.cgroup;
- task_cgrp = mem_cgroup_from_task(p)->css.cgroup;

rcu_read_lock();
- ret = cgroup_path(task_cgrp, task_memcg_name, PATH_MAX);
+
+ mem_cgrp = memcg->css.cgroup;
+ task_cgrp = task_cgroup(p, mem_cgroup_subsys_id);
+
+ ret = cgroup_path(task_cgrp, memcg_name, PATH_MAX);
if (ret < 0) {
/*
* Unfortunately, we are unable to convert to a useful name
@@ -760,16 +761,22 @@ void mem_cgroup_print_oom_info(struct mem_cgroup *memcg, struct task_struct *p)
rcu_read_unlock();
goto done;
}
+ rcu_read_unlock();
+
+ printk(KERN_INFO "Task in %s killed", memcg_name);
+
+ rcu_read_lock();
ret = cgroup_path(mem_cgrp, memcg_name, PATH_MAX);
if (ret < 0) {
rcu_read_unlock();
goto done;
}
-
rcu_read_unlock();

- printk(KERN_INFO "Task in %s killed as a result of limit of %s\n",
- task_memcg_name, memcg_name);
+ /*
+ * Continues from above, so we don't need an KERN_ level
+ */
+ printk(" as a result of limit of %s\n", memcg_name);
done:

printk(KERN_INFO "memory: usage %llukB, limit %llukB, failcnt %llu\n",
--
Balbir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/