linux-kernel - Re: [PATCH] f2fs: use inode_lock_shared instead of inode_lock in f2fs_seek

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

Message-ID: <46d5e083-6e85-1e92-8123-3d0c7579c79f@kernel.org>
Date:   Tue, 7 Nov 2023 22:16:53 +0800
From:   Chao Yu <chao@...nel.org>
To:     zhangxirui <xirui.zhang@...o.com>, jaegeuk@...nel.org
Cc:     linux-f2fs-devel@...ts.sourceforge.net,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] f2fs: use inode_lock_shared instead of inode_lock in
 f2fs_seek_block()

On 2023/10/21 20:19, zhangxirui wrote:
> inode_lock_shared() -> down_read(&inode->i_rwsem)
>         inode_lock() -> down_write(&inode->i_rwsem)
> 
> Inode is not updated in f2fs_seek_block(), so there is no need
> to hold write lock, use read lock for more efficiency.
> 
> Signed-off-by: zhangxirui <xirui.zhang@...o.com>

Reviewed-by: Chao Yu <chao@...nel.org>

Thanks,