linux-kernel - Re: [PATCH mmotm 1/2] memcg: add interface to reset limits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Jun 2009 14:43:47 +0900
From:	Daisuke Nishimura <nishimura@....nes.nec.co.jp>
To:	Li Zefan <lizf@...fujitsu.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-mm <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Paul Menage <menage@...gle.com>,
	Daisuke Nishimura <nishimura@....nes.nec.co.jp>
Subject: Re: [PATCH mmotm 1/2] memcg: add interface to reset limits

On Wed, 03 Jun 2009 13:16:27 +0800, Li Zefan <lizf@...fujitsu.com> wrote:
> Daisuke Nishimura wrote:
> > Setting mem.limit or memsw.limit to 0 has no meaning
> > in actual use(no process can run in such condition).
> > 
> 
> I wrote a test program that set mem.limit to 0 to test
> oom in memcg, and now it is in LTP, though I can modify
> it accordingly.
> 
Thank you for your information, there is an acutual user then.

> > We don't have interface to reset mem.limit or memsw.limit now,
> > so let's reset the mem.limit or memsw.limit to default(unlimited)
> > when they are being set to 0.
> > 
> 
> The idea of having a way to set the limit to unlimited is good,
> but how about allow this by writing -1 to mem.limit?
> 
O.K.
I'll try it.


Thanks,
Daisuke Nishimura.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/