| 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
| ||
|
Message-Id: <20090115120829.e1d417e8.kamezawa.hiroyu@jp.fujitsu.com> Date: Thu, 15 Jan 2009 12:08:29 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> Cc: balbir@...ux.vnet.ibm.com, Daisuke Nishimura <nishimura@....nes.nec.co.jp>, LKML <linux-kernel@...r.kernel.org>, linux-mm <linux-mm@...ck.org>, Andrew Morton <akpm@...ux-foundation.org>, Pavel Emelyanov <xemul@...nvz.org>, Li Zefan <lizf@...fujitsu.com>, Paul Menage <menage@...gle.com> Subject: Re: [RFC][PATCH 5/4] memcg: don't call res_counter_uncharge when obsolete On Thu, 15 Jan 2009 11:48:46 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote: > On Wed, 14 Jan 2009 19:25:39 +0530 > Balbir Singh <balbir@...ux.vnet.ibm.com> wrote: > > I liked the earlier, EBUSY approach that ensured that parents could > > not go away if children exist. IMHO, the code has gotten too complex > > and has too many corner cases. Time to revisit it. > > > It's on my plan. > I'll fix this by CSS-ID patch. > > When I recored memcg's CSS-ID to swap_cgroup (not pointer to memcg), > we never need memcg's refcnt. > Sorry, ignore this. refcnt in memcg is necessary anyway to prevent reuse of ID. -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