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] [day] [month] [year] [list]
Message-Id: <20080311192338.9f89ca70.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Tue, 11 Mar 2008 19:23:38 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	balbir@...ux.vnet.ibm.com
Cc:	Li Zefan <lizf@...fujitsu.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Menage <menage@...gle.com>,
	Pavel Emelianov <xemul@...nvz.org>,
	LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
	Linux Containers <containers@...ts.osdl.org>
Subject: Re: [PATCH 2/3] memcg: put a restriction on writing
 memory.force_empty

On Tue, 11 Mar 2008 15:45:06 +0530
Balbir Singh <balbir@...ux.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

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ