LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* [PATCH 2/3] memcg: put a restriction on writing memory.force_empty
@ 2008-03-11 10:08 Li Zefan
2008-03-11 10:15 ` Balbir Singh
0 siblings, 1 reply; 3+ messages in thread
From: Li Zefan @ 2008-03-11 10:08 UTC (permalink / raw)
To: Andrew Morton
Cc: Balbir Singh, KAMEZAWA Hiroyuki, Paul Menage, Pavel Emelianov,
LKML, linux-mm, Linux Containers
We can write whatever to memory.force_empty:
echo 999 > memory.force_empty
echo wow > memory.force_empty
This is odd, so let's make '1' to be the only valid value.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
mm/memcontrol.c | 21 ++++++++++++---------
1 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index eb681a6..6145031 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -868,15 +868,18 @@ static ssize_t mem_cgroup_write(struct cgroup *cont, struct cftype *cft,
mem_cgroup_write_strategy);
}
-static ssize_t mem_force_empty_write(struct cgroup *cont,
- struct cftype *cft, struct file *file,
- const char __user *userbuf,
- size_t nbytes, loff_t *ppos)
+static int mem_force_empty_write(struct cgroup *cont, struct cftype *cft,
+ u64 val)
{
- struct mem_cgroup *mem = mem_cgroup_from_cont(cont);
- int ret = mem_cgroup_force_empty(mem);
- if (!ret)
- ret = nbytes;
+ struct mem_cgroup *mem;
+ int ret;
+
+ if (val != 1)
+ return -EINVAL;
+
+ mem = mem_cgroup_from_cont(cont);
+ ret = mem_cgroup_force_empty(mem);
+
return ret;
}
@@ -935,7 +938,7 @@ static struct cftype mem_cgroup_files[] = {
},
{
.name = "force_empty",
- .write = mem_force_empty_write,
+ .write_u64 = mem_force_empty_write,
},
{
.name = "stat",
--
1.5.4.rc3
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 2/3] memcg: put a restriction on writing memory.force_empty
2008-03-11 10:08 [PATCH 2/3] memcg: put a restriction on writing memory.force_empty Li Zefan
@ 2008-03-11 10:15 ` Balbir Singh
2008-03-11 10:23 ` KAMEZAWA Hiroyuki
0 siblings, 1 reply; 3+ messages in thread
From: Balbir Singh @ 2008-03-11 10:15 UTC (permalink / raw)
To: Li Zefan
Cc: Andrew Morton, KAMEZAWA Hiroyuki, Paul Menage, Pavel Emelianov,
LKML, linux-mm, Linux Containers
Li Zefan wrote:
> We can write whatever to memory.force_empty:
>
> echo 999 > memory.force_empty
> echo wow > memory.force_empty
>
> This is odd, so let's make '1' to be the only valid value.
I suspect as long as there is no unreasonable side-effect, writing 999 or wow
should be OK.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 2/3] memcg: put a restriction on writing memory.force_empty
2008-03-11 10:15 ` Balbir Singh
@ 2008-03-11 10:23 ` KAMEZAWA Hiroyuki
0 siblings, 0 replies; 3+ messages in thread
From: KAMEZAWA Hiroyuki @ 2008-03-11 10:23 UTC (permalink / raw)
To: balbir
Cc: Li Zefan, Andrew Morton, Paul Menage, Pavel Emelianov, LKML,
linux-mm, Linux Containers
On Tue, 11 Mar 2008 15:45:06 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> Li Zefan wrote:
> > We can write whatever to memory.force_empty:
> >
> > echo 999 > memory.force_empty
> > echo wow > memory.force_empty
> >
> > This is odd, so let's make '1' to be the only valid value.
>
> I suspect as long as there is no unreasonable side-effect, writing 999 or wow
> should be OK.
>
I agree with Balbir.
Thanks,
-Kame
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-03-11 10:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-11 10:08 [PATCH 2/3] memcg: put a restriction on writing memory.force_empty Li Zefan
2008-03-11 10:15 ` Balbir Singh
2008-03-11 10:23 ` KAMEZAWA Hiroyuki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).