linux-kernel - Re: [PATCH 3/3] kernfs: change kernfs_rename

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: <ZADvyJcIazbpCnPu@casper.infradead.org>
Date:   Thu, 2 Mar 2023 18:49:44 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     Imran Khan <imran.f.khan@...cle.com>
Cc:     tj@...nel.org, gregkh@...uxfoundation.org, viro@...iv.linux.org.uk,
        linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        joe.jin@...cle.com
Subject: Re: [PATCH 3/3] kernfs: change kernfs_rename_lock into a read-write
 lock.

On Thu, Mar 02, 2023 at 03:32:03PM +1100, Imran Khan wrote:
> kernfs_rename_lock protects a node's ->parent and thus kernfs topology.
> Thus it can be used in cases that rely on a stable kernfs topology.
> Change it to a read-write lock for better scalability.
> 
> Suggested by: Al Viro <viro@...iv.linux.org.uk>
> Signed-off-by: Imran Khan <imran.f.khan@...cle.com>

Reviewed-by: Matthew Wilcox (Oracle) <willy@...radead.org>