mirror of
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
synced 2025-01-10 10:33:32 +08:00
f76344fb6f
This was actually caused by two bugs. The first bug is that if the inode has been fully fixed up, the code will attempt to remove the inode from the inode_bad_map without checking to see if this bitmap is present. Since it is cleared at the end of pass 2, if e2fsck_process_bad_inode is called in pass 4 (as it is for disconnected inodes), this would result in a core dump. The first bug was mostly hidden by a second bug, which caused e2fsck_process_bad_inode() to consider all inodes without an extended attribute to be not fixed. Note: This bug was introduced in e2fsprogs 1.36. (Addresses Debian Bug: #316736) |
||
|---|---|---|
| .. | ||
| expect.1 | ||
| expect.2 | ||
| image.gz | ||
| name | ||