linux-kernel - Re: [PATCH 17/18] fs: icache remove inode

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: <20101013112827.GC16422@infradead.org>
Date:	Wed, 13 Oct 2010 07:28:27 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Nick Piggin <npiggin@...nel.dk>
Cc:	Dave Chinner <david@...morbit.com>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 17/18] fs: icache remove inode_lock

On Wed, Oct 13, 2010 at 06:27:01PM +1100, Nick Piggin wrote:
> I'm happy to help to port the top of the patch set onto changes in
> earlier parts of it, but I would like the chance to do this really. I'm
> back in action now, so I can spend a lot of time catching up.

That's all good and fine, but it's really no reason for delaying getting
the most important bits in.  RCU path walk is all good and fine, and
I'm really looking forward to eventually see it.  But the basic
inode_lock and dcache_lock splits are fundamental work we need rather
sooner than later.  Additional candy ontop of that is fine but we'll
need a solid base.  Also note that having the locking split up, and
proper exported APIs instead of growling into dcache internals in
various filesystems means that we can start to look into replacing
the global inode and dcache hashes much more easily, and having
global data structures at least for the dcache is almost as bad
as having global locks.

--
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/