linux-kernel - Re: [PATCH 02/17] fs: icache lock s

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101001054909.GB32349@infradead.org>
Date:	Fri, 1 Oct 2010 01:49:09 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Dave Chinner <david@...morbit.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 02/17] fs: icache lock s_inodes list

On Wed, Sep 29, 2010 at 10:18:34PM +1000, Dave Chinner wrote:
> From: Nick Piggin <npiggin@...e.de>
> 
> To allow removal of the inode_lock, we first need to protect the
> superblock inode list with it's own lock instead of using the
> inode_lock for this purpose. Nest the new sb_inode_list_lock inside
> the inode_lock around the list operations it needs to protect.

Is there any good reason not to make this lock per-superblock?

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