linux-kernel - Re: vfsmount lock issues on very large ppc64 box

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110717010427.GC5359@parisc-linux.org>
Date:	Sat, 16 Jul 2011 19:04:28 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Anton Blanchard <anton@...ba.org>
Cc:	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 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.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/