linux-kernel - Re: [PATCH 1/2] mm/filemap: fix miscalculated file range for filemap_fdatawrite_range

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: <64379346-a39b-4903-b861-0e25e9e79821@kernel.dk>
Date: Wed, 19 Feb 2025 09:25:16 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Jingbo Xu <jefflexu@...ux.alibaba.com>, linux-fsdevel@...r.kernel.org,
 linux-mm@...ck.org
Cc: brauner@...nel.org, linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk
Subject: Re: [PATCH 1/2] mm/filemap: fix miscalculated file range for
 filemap_fdatawrite_range_kick()

On 2/18/25 5:02 AM, Jingbo Xu wrote:
> iocb->ki_pos has been updated with the number of written bytes since
> generic_perform_write().
> 
> Besides __filemap_fdatawrite_range() accepts the inclusive end of the
> data range.

Fix looks good, this got introduced because the logic got moved into
generic_write_sync() rather than being a separate helper.

Reviewed-by: Jens Axboe <axboe@...nel.dk>

-- 
Jens Axboe