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
| ||
|
Date: Fri, 17 Aug 2012 11:04:02 +0400 From: Glauber Costa <glommer@...allels.com> To: Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com> CC: <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>, <cgroups@...r.kernel.org>, <devel@...nvz.org>, Michal Hocko <mhocko@...e.cz>, Johannes Weiner <hannes@...xchg.org>, Andrew Morton <akpm@...ux-foundation.org>, Christoph Lameter <cl@...ux.com>, David Rientjes <rientjes@...gle.com>, Pekka Enberg <penberg@...nel.org>, Pekka Enberg <penberg@...helsinki.fi> Subject: Re: [PATCH v2 06/11] memcg: kmem controller infrastructure On 08/17/2012 06:36 AM, Kamezawa Hiroyuki wrote: > I just want to see the same logic used in mem_cgroup_uncharge_common(). > Hmm, at setting pc->mem_cgroup, the things happens in > set pc->mem_cgroup > set Used bit > order. If you clear pc->mem_cgroup > unset Used bit > clear pc->mem_cgroup > seems reasonable. Makes sense. I'll make sure we're consistent here. -- 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