[DragonFlyBSD - Bug #3451] ext2fs: read ext4 extent-mapped inodes (read-only)

[sigttou]

Issue #3451 has been updated by sigttou.


Wasn't aware of the PR. Let me check if I can combine these 3 in a meaningful way.

----------------------------------------
Bug #3451: ext2fs: read ext4 extent-mapped inodes (read-only)
http://bugs.dragonflybsd.org/issues/3451#change-14863

* Author: sigttou
* Status: New
* Priority: Normal
* Category: Driver
* Target version: 6.6
* Start date: 2026-10-16
----------------------------------------
@ext2fs@ advertises @EXT2F_INCOMPAT_EXTENTS@, but the extent lookup path is
stubbed out: @ext4_bmapext()@ and @ext4_ext_find_extent()@ both return @EINVAL at . @mkfs.ext4@ creates every
inode extent-mapped by default, so a read-only mount of a Linux ext4 filesystem succeeds (@statfs@
reads only the superblock) but every directory lookup and @readdir@ fails with @EINVAL at .

Port the read-only extent tree walk and the extent bmap from FreeBSD main
(d7d237ce731f), following the extent read path (d7511a40a749, b394cd1e28f1, 5679656e09fb).

The extent write path (allocation, truncation and removal) remains unimplemented.

The second patch is required for @metadata_csum@ filesystems (directory block checksums)

---Files--------------------------------
0001-ext2fs-read-ext4-extent-mapped-inodes.patch (14.1 KB)
0002-ext2fs-do-not-synthesize-a-generation-number-on-inod.patch (1.58 KB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account