linux-kernel - Re: [RESEND PATCH v3] xfs: fix the entry condition of exact EOF block allocation optimization

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: <173806186643.500545.9968635452635594761.b4-ty@kernel.org>
Date: Tue, 28 Jan 2025 11:57:46 +0100
From: Carlos Maiolino <cem@...nel.org>
To: dchinner@...hat.com, djwong@...nel.org, 
 Jinliang Zheng <alexjlzheng@...il.com>
Cc: chandanbabu@...nel.org, linux-xfs@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Jinliang Zheng <alexjlzheng@...cent.com>, 
 Dave Chinner <david@...morbit.com>
Subject: Re: [RESEND PATCH v3] xfs: fix the entry condition of exact EOF
 block allocation optimization

On Wed, 15 Jan 2025 20:35:25 +0800, Jinliang Zheng wrote:
> When we call create(), lseek() and write() sequentially, offset != 0
> cannot be used as a judgment condition for whether the file already
> has extents.
> 
> Furthermore, when xfs_bmap_adjacent() has not given a better blkno,
> it is not necessary to use exact EOF block allocation.
> 
> [...]

Applied to for-next, thanks!

[1/1] xfs: fix the entry condition of exact EOF block allocation optimization
      commit: 915175b49f65d9edeb81659e82cbb27b621dbc17

Best regards,
-- 
Carlos Maiolino <cem@...nel.org>