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@xxxxxxxxxx>
