linux-kernel - Re: [PATCH 3/3] memcgoup: allow memory.failcnt to be reset

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: <47D9BAA6.4010409@cn.fujitsu.com>
Date:	Fri, 14 Mar 2008 08:37:10 +0900
From:	Li Zefan <lizf@...fujitsu.com>
To:	balbir@...ux.vnet.ibm.com
CC:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...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 3/3] memcgoup: allow memory.failcnt to be reset

Balbir Singh wrote:
> KAMEZAWA Hiroyuki wrote:
>> On Tue, 11 Mar 2008 19:09:02 +0900
>> Li Zefan <lizf@...fujitsu.com> wrote:
>>
>>> Allow memory.failcnt to be reset to 0:
>>>
>>>         echo 0 > memory.failcnt
>>>
>>> And '0' is the only valid value.
>>>
>> Can't this be generic resource counter function ?
>>
> 
> I was about to suggest a generic cgroup option, since we do reset values even
> for the cpu accounting subsystem.
> 

It won't help. You still have to write the write function, and you have to call
some res_counter routines to reset the value, and maybe also do some other
work.

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