| 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: <20110717084630.GC8006@one.firstfloor.org> Date: Sun, 17 Jul 2011 10:46:30 +0200 From: Andi Kleen <andi@...stfloor.org> To: Matthew Wilcox <matthew@....cx> Cc: Anton Blanchard <anton@...ba.org>, npiggin@...nel.dk, viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>, Tim Chen <tim.c.chen@...ux.intel.com> Subject: Re: vfsmount lock issues on very large ppc64 box On Sat, Jul 16, 2011 at 07:04:28PM -0600, Matthew Wilcox wrote: > On Sun, Jul 17, 2011 at 10:50:27AM +1000, Anton Blanchard wrote: > > Looking closer, all of these calls are in pipefs and sockfs. > > Since we never mount either filesystem they never get a long term > > reference and we always end up in the very slow write brlock path > > that takes a lock for each online CPU. > > > > Here is a quick hack that takes a long term reference on pipefs > > and sockfs which fixes the problem. Any thoughts on how we should > > fix it properly? > > I know Tim and Andi have been looking into this ... I forget what their > fix was though. Tim posted a patch, but it wasn't applied for unknown reasons. https://lkml.org/lkml/2011/4/13/561 -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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