linux-ext4 - Re: 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-prev] [day] [month] [year] [list]

Date:   Mon, 27 Apr 2020 20:15:32 +0530
From:   Ritesh Harjani <riteshh@...ux.ibm.com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: ext4 fiemap and the inode lock

Hello Christoph,

On 4/27/20 4:20 PM, Christoph Hellwig wrote:
> 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?

So, maybe since maybe the request was only to provide the block mapping
and since extent path didn't have it - so I may have not added it into
the indirect block case as well. Assuming both anyways uses same
-> i_data_sem lock. But I am not sure if it was deliberately dropped,
otherwise I would have noted that in my cover letter. So maybe it got
missed. But I will try and search in internal dev branches too, to see
if I could find anything related to that.

Thanks for noting that.

-ritesh