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, 12 Dec 2008 10:12:57 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: Paul Menage <menage@...gle.com> Cc: balbir@...ux.vnet.ibm.com, containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org Subject: Re: [RFC][PATCH 2/3] CGroups: Use hierarchy_mutex in memory controller On Thu, 11 Dec 2008 09:05:47 -0800 Paul Menage <menage@...gle.com> wrote: > On Wed, Dec 10, 2008 at 10:53 PM, KAMEZAWA Hiroyuki > <kamezawa.hiroyu@...fujitsu.com> wrote: > > > > Could you write a document to explain what kind of nest of locks are allowed > > before merging this ? > > We should probably treat it similarly to the cpuset "callback_mutex". > I.e. memory allocations are most likely forbidden when you're holding > it. > Hmm. Anyway, hierarchy mutex should not be aquired in deep stack of the kernel calls. (and my patch will make memcg's hierarchy walk lockless.) -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