linux-kernel - Re: [patch 08/14] fs: scale inode alias list

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: <20090330123107.GH31000@wotan.suse.de>
Date:	Mon, 30 Mar 2009 14:31:07 +0200
From:	Nick Piggin <npiggin@...e.de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 08/14] fs: scale inode alias list

On Mon, Mar 30, 2009 at 02:18:07PM +0200, Andi Kleen wrote:
> npiggin@...e.de writes:
> 
> > Add a new lock, dcache_inode_lock, to protect the inode's i_dentry list
> > from concurrent modification. d_alias is also protected by d_lock.
> 
> This would seem to ask for per object lock? Why not put it into the inode?

Yes, this comes later in the last patch, because the first round is just
meant to be as simple as possible, and making it per-inode is non-trivial
(not too difficult, but just not totally trivial) for reasons given in
that patch changelog.
--
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/