git: ext2fs: do not synthesize a generation number on inode lookup

Aaron LI aly at crater.dragonflybsd.org
Fri Oct 23 06:19:04 PDT 2026


commit afaef3c86db6aff699871a4e799b7806c7b6775f
Author: David Bidner <david at crap.solutions>
Date:   Thu Oct 22 14:03:49 2026 +0200

    ext2fs: do not synthesize a generation number on inode lookup
    
    ext2_vget() replaced an on-disk generation number of 0 with a random
    value.  On ext4 with metadata_csum the generation number is part of the
    inode, directory entry and extent block checksums, so the in-memory
    change makes every directory block checksum fail and reads return EIO.
    
    FreeBSD removed this in 43ce40e891e1 ("ext2fs: cleanup generation
    number management"); ext2fs already generates a non-zero value at
    inode allocation time.
    
    Bug: https://bugs.dragonflybsd.org/issues/3451

Summary of changes:
 sys/vfs/ext2fs/ext2_vfsops.c | 9 ---------
 1 file changed, 9 deletions(-)

http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/afaef3c86db6aff699871a4e799b7806c7b6775f


-- 
DragonFly BSD source repository


More information about the Commits mailing list