ext4: fix FS_IOC_GETFSMAP handling

Browse source

The original implementation ext4's FS_IOC_GETFSMAP handling only
worked when the range of queried blocks included at least one free
(unallocated) block range.  This is because how the metadata blocks
were emitted was as a side effect of ext4_mballoc_query_range()
calling ext4_getfsmap_datadev_helper(), and that function was only
called when a free block range was identified.  As a result, this
caused generic/365 to fail.

Fix this by creating a new function ext4_getfsmap_meta_helper() which
gets called so that blocks before the first free block range in a
block group can get properly reported.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@vger.kernel.org

...

This commit is contained in:

Theodore Ts'o 2024-10-23 00:25:37 -04:00

parent 40eb3104cf

commit 4a622e4d47

3 changed files with 68 additions and 5 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

54

fs/ext4/fsmap.c

View file

18

fs/ext4/mballoc.c

View file

1

fs/ext4/mballoc.h

View file