[DragonFlyBSD - Bug #3458] (Resolved) ext2fs: inode bitmap of an rmdir'd inode is not written at unmount

[liweitianux]

Issue #3458 has been updated by liweitianux.

Status changed from New to Resolved

Patch merged. Thank you.

----------------------------------------
Bug #3458: ext2fs: inode bitmap of an rmdir'd inode is not written at unmount
http://bugs.dragonflybsd.org/issues/3458#change-14912

* Author: sigttou
* Status: Resolved
* Priority: Normal
* Category: Kernel
* Target version: 6.6
* Start date: 2026-10-22
----------------------------------------
The inode bitmap update for an inode freed by @rmdir@ stays dirty on the device vnode during @vflush()@ and is written after the clean flag, or lost. After @mkdir@, @rmdir@ and @umount@, @e2fsck -fn@ reports an inode bitmap difference (@rc 4@). @ffs_flushfiles()@ does @VOP_FSYNC(devvp, MNT_WAIT)@ at that point. Do the same in the ext2 flush path, under @vn_lock@ and only for a read-write mount.


---Files--------------------------------
0001-ext2fs-sync-the-device-vnode-before-writing-the-clea.patch (1.69 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