On Tue, 05 Aug 2025 14:00:30 +0530, Ojaswin Mujoo wrote:
> With bigalloc enabled, the logic to report last extent has a bug since
> we try to use cluster units instead of block units. This can cause an issue
> where extra incorrect entries might be returned back to the user. This was
> flagged by generic/365 with 64k bs and -O bigalloc.
>
> ** Details of issue **
>
> [...]
Applied, thanks!
[1/2] ext4: Fix fsmap end of range reporting with bigalloc
commit: bae76c035bf0852844151e68098c9b7cd63ef238
[2/2] ext4: Fix reserved gdt blocks handling in fsmap
commit: 3ffbdd1f1165f1b2d6a94d1b1aabef57120deaf7
Best regards,
--
Theodore Ts'o <tytso@xxxxxxx>
