aboutsummaryrefslogtreecommitdiffstats
path: root/tests/f_bad_disconnected_inode
Commit message (Collapse)AuthorAgeFilesLines
* Switch back to 1.42.9 now that there is a fixJP Abgrall2014-03-191-9/+0
| | | | | | Revert "Revert changes that moved from 1.41.14 to 1.42.9" This reverts commit 65f0aab98b20b5994a726ab90d355248bcddfffd.
* Revert changes that moved from 1.41.14 to 1.42.9JP Abgrall2014-03-061-0/+9
| | | | | | | | | | | | | | | | Revert "e2fsck: Don't use e2fsck_global_ctx unless HAVE_SIGNAL_H" commit e80e74c41d85ff93f3d212ba6512340f48054a93. Revert "Merge remote-tracking branch 'linaro/linaro-1.42.9' into aosp_master" This reverts commit e97b2b6fc82f840e84dfc631b87f21be44ff2421, reversing changes made to 7e2fb9d09c245eba70ee008b78007315e9c0f1df. Revert "Prepare for upstream 1.42.9" This reverts commit 7e2fb9d09c245eba70ee008b78007315e9c0f1df. Bug: 13340735 Change-Id: If48b153a95ef5f69f7cdccb00e23524abff3c5a8 Signed-off-by: JP Abgrall <jpa@google.com>
* e2fsck: remove EXT4_EOFBLOCKS_FL flag handlingLukas Czerner2012-03-221-9/+0
| | | | | | | | | | | | | | | | | | | We've decided to remove EOFBLOCKS_FL from the ext4 file system entirely, because it is not actually very useful and it is causing more problems than it solves. We're going to remove it from e2fsprogs first and then after the new e2fsprogs version is common enough we can remove the kernel part as well. This commit changes e2fsck to not check for EOFBLOCKS_FL. Instead we simply search for initialized extents past the i_size as this should not happen. Uninitialized extents can be past the i_size as we can do fallocate with KEEP_SIZE flag. Also remove the EXT4_EOFBLOCKS_FL from lib/ext2fs/ext2_fs.h since it is no longer needed. Signed-off-by: Lukas Czerner <lczerner@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* libext2fs: ext2fs_[set_]file_acl_block needs to check for 64-bit feature flagTheodore Ts'o2011-10-161-2/+2
| | | | | | | | | | | | | | | | The ext2fs_file_acl_block() and ext2fs_set_file_acl_block() needs to only check i_file_acl_high if the 64-bit flag is set. This is needed because otherwise we will run into problems on Hurd systems which actually use that field for h_i_mode_high. This involves an ABI change since we need to pass ext2_filsys to these functions. Fortunately these functions were first included in the 1.42-WIP series, so it's OK for us to change them now. (This is why we have 1.42-WIP releases. :-) Addresses-Sourceforge-Bug: #3379227 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
* Merge branch 'maint' into nextTheodore Ts'o2010-06-071-0/+9
|\ | | | | | | | | | | | | | | Conflicts: e2fsck/journal.c e2fsck/pass1.c e2fsck/pass2.c misc/mke2fs.c
| * e2fsck: Check for cases where EOFBLOCKS_FL is unnecessarily setTheodore Ts'o2010-05-101-0/+9
| | | | | | | | | | | | | | | | | | | | Some kernels will crash if EOFBLOCKS_FL is set when it is it not needed, and this if it is left set when it isn't needed, it is a sign of a kernel bug. Addresses-Google-Bug: #2604224 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
* | Use ext2fs_file_acl_block() instead of using .i_file_acl directlyValerie Aurora Henson2009-09-071-2/+2
|/ | | | | | | This provides support for 48-bit file acl blocks. Signed-off-by: Valerie Aurora Henson <vaurora@redhat.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
* e2fsck: Add support for extentsTheodore Ts'o2008-02-182-27/+13
| | | | Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
* On-disk format definition for huge filesTheodore Ts'o2006-11-111-4/+1
| | | | | | | | | | | - EXT4_FEATURE_RO_COMPAT_HUGE_FILE (0x0008) - change i_blocks to be in units of s_blocksize units instead of 512-byte sectors, use l_i_frag and l_i_fsize as i_blocks_hi (could also be part of 64BIT). E2fsck and debugfs changed to support i_blocks_hi instead of l_i_frag and l_i_fsize. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
* [BUGFIX]: E2fsck will segfault on disconnected inode with extended attribute(s)Theodore Ts'o2005-07-044-0/+77
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)