linux-ext4 - ext4 fiemap and the inode lock

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

Message-ID: <20200427105032.GA27494@infradead.org>
Date:   Mon, 27 Apr 2020 03:50:32 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Ritesh Harjani <riteshh@...ux.ibm.com>
Cc:     linux-ext4@...r.kernel.org
Subject: ext4 fiemap and the inode lock

Hi Ritesh,

before you converted ext4 to use iomap for fiemap, the indirect block
case used generic_block_fiemap and thus took i_rwsem around the 
actual fiemap operation.  Do you remember if you did an audit if it
was ok to drop it, or did that just slip in?