linux-ext4 - Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked dirty

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: <20191016064353.GA25846@infradead.org>
Date:   Tue, 15 Oct 2019 23:43:53 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Dave Chinner <david@...morbit.com>
Cc:     linux-xfs@...r.kernel.org, linux-ext4@...r.kernel.org,
        linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2] iomap: iomap that extends beyond EOF should be marked
 dirty

I wonder if the i_size check should be done in core, similar to the
iomap_block_needs_zeroing helper.  But independent of what is nicer
this version does look correct to me:

Reviewed-by: Christoph Hellwig <hch@....de>