vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit de7ca106a087a5c63a85c0b8a90b6f0743002f52
Merge: de8c3ae2 68e00dc5
Author: Theodore Ts'o <tytso@mit.edu>
Date: Thu Mar 7 00:47:54 2019 -0500
Merge tag 'v1.45.0' into debian/master
v1.45.0
commit de8c3ae250ac124c20c4f0301833a89bd47d4dca
Merge: 346a9922 a92fbdd9
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Mar 5 23:40:34 2019 -0500
Merge tag 'v1.44.6' into debian/master
v1.44.6
commit 346a9922a21adae73187ed60c6caaf493ca1e3bc
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sun Dec 16 00:54:28 2018 -0500
Remove debian patches for v1.44.4 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 9897e1aa1a6ef900f39e225d5b508c4801e3afa9
Merge: 1e44f35d 9a03c07e
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sun Dec 16 00:52:33 2018 -0500
Merge tag 'v1.44.5' into debian/master
v1.44.5
commit 1e44f35dcf235192bc1d4fb1b1d78547127201d7
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Aug 21 11:32:30 2018 -0400
debian: update changelog for 1.44.4-2 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 600e95380e5c168050b15c6a743522b744d27520
Author: Theodore Ts'o <tytso@mit.edu>
Date: Wed Aug 22 16:33:10 2018 -0400
debian: remove hard-coded dependency for libss2 in e2fsprogs.shlibs.local
The hard-coded override is very old, and isn't necessary --- in fact,
it's actively harmful because we are using one or two symbols that
were added to libss2 after e2fsprogs 1.34. So remove it.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit fcfd0c92df11a423d23b7273735e39c125d9d4a9
Author: Theodore Ts'o <tytso@mit.edu>
Date: Wed Aug 22 14:55:22 2018 -0400
debian: fix up libcom-err2's version dependency handling
We renamed libcomerr2 to libcom-err2 in 1.43.9. So generating
dependencies of the form libcom-err2 (>= 1.34) don't really make any
sense.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 72159760cc09998262bcfa5556816c87a03ff964
Author: Theodore Ts'o <tytso@mit.edu>
Date: Wed Aug 22 01:00:10 2018 -0400
Add patch: Make sure all release note files have a single trailing empty line
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 4af763a5faebb807d6486161f5ff05f69120c20d
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Aug 21 20:12:08 2018 -0400
debian: update to debian policy 4.2.0
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 674b6dce64e9019626f893eada6475ba625adb82
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Aug 21 20:10:02 2018 -0400
debian: create NEWS.gz in /usr/share/doc/e2fsprogs
Create the full NEWS.gz and put it in /usr/share/doc/e2fsprogs instead
of the RELEASE-NOTES file to comply with the Debian policy 4.2.0.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 6155f314928a21d9d1c645758cd394988a9d1785
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Aug 21 16:27:51 2018 -0400
Cherry-pick "e2fsck: allow verity files to have initialized blocks past i_size"
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 5c36535a6fc0435e19aa5347b83e960deb536757
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Aug 21 10:55:07 2018 -0400
Rediff patches for 1.44.4-2 release
Add 0001-tune2fs-fix-dereference-of-freed-memory-after-journa.patch
Add 0002-libe2p-fix-verity-flag-bit.patch
Add 0003-libext2fs-add-verity-flag-to-EXT2_LIB_FEATURE_RO_COM.patch
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit eee05549b68661a58c5f2aac1101e24d5c292072
Merge: 0e4727e8 40e66e2e
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Aug 18 22:50:55 2018 -0400
Merge tag 'v1.44.4' into debian/master
v1.44.4
commit 0e4727e896905ba29e6f635267c109fb316b2b4d
Merge: 625f3ef5 85e53f42
Author: Theodore Ts'o <tytso@mit.edu>
Date: Fri Aug 17 23:01:24 2018 -0400
Merge tag 'v1.44.3' into debian-packaging
v1.44.3
commit 625f3ef536be33343f13e7846d53d73bb54bc7ad
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon May 14 20:23:58 2018 -0400
debian: remove debian patatches from v1.44.1-2
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 2c0302e8bc43f7e66f163c587960906d808c3249
Merge: 83b42b68 ff466404
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon May 14 20:23:40 2018 -0400
Merge branch 'maint' into debian-packaging
commit ff4664047dd27eefd98568f48c1d5c1efe1b3668
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon May 14 20:12:59 2018 -0400
Update release notes, etc., for the 1.44.1 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit a64eb3bd31a8f3b870b916fa734e5696210c270d
Author: Jakub Bogusz <qboosh@pld-linux.org>
Date: Mon May 14 19:57:37 2018 -0400
po: update pl.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 72c963164c06397cf725e1d619274d83021beba4
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon May 14 19:16:26 2018 -0400
debian: demote e2fsprogs from Essential: yes to XB-Important: yes
Addresses-Debian-Bug: #474540
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 61d16c39ff93f3da4ba9e2f6ee1359d48a2da969
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon May 14 18:22:09 2018 -0400
mke2fs: print error string if ext2fs_close_free() fails
There are multiple reasons why ext2fs_close_free() might fail, not
just an I/O error while writing out a backup superblock. Print the
error code, and then allow mke2fs to exit with an exit status code of
1, instead of whatever random error code ext2fs_close_free() might
have returned with.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit e707b74145b96e62fcea41a7939b8fe26746bb1b
Author: bjornpagen@gmail.com <bjornpagen@gmail.com>
Date: Sun May 13 22:07:40 2018 -0400
Use @AR@ instead of hardcoded 'ar'
e2fsprogs currently hardcodes 'ar' in one of it's makefiles. This is
fixed with this patch:
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 8785aaead7d8e1bdf66be06f97e01cc9416d363d
Author: Lukas Czerner <lczerner@redhat.com>
Date: Tue Apr 10 14:09:33 2018 +0200
e2fsprogs: fix Free Software Foundation address
This is mostly automatic replace of Free Software Foundation address in
all our files with the correct address that can be found at
http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit d3f01729bff29e75b21994dc305e09fb055baff3
Author: Lukas Czerner <lczerner@redhat.com>
Date: Fri Apr 13 14:27:49 2018 +0200
chattr.1: 'a' and 'i' attribute do not affect existing file descriptors
Change chattr man page to make it clear that 'i' and 'a' attributes
does not affect the ability to write to already existing file
descriptors
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit d5bd126cd6a06dd2a8652557776ea298fb442912
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Apr 10 11:04:50 2018 -0400
debian: add changelog entry for 1.44.1-2 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 83b42b683f7c9a550d03a2f2242a3bc975518ed6
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Apr 10 11:04:50 2018 -0400
debian: add changelog entry for 1.44.1-2 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 39299ed61065d76b4b09f0b9a1be84a823c43451
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Apr 9 16:31:27 2018 -0400
Add debian patches for commits cherry picked since v1.44.1-1
(Also remove tests/f_orphquot since it has a binary file which makes
debian's patch infrastructure unhappy.)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 3bf5261174ed55a2e7050c46838a16c08174b198
Author: Lukas Czerner <lczerner@redhat.com>
Date: Mon Apr 9 11:58:15 2018 -0400
e2image: fix metadata image handling on big endian systems
Currently e2image metadata image handling and creating is completely
broken on big endian systems. It just does not care about endianness at
all. This was uncovered With addition of i_bitmaps test, which is the
first test that actually tests e2image metadata image.
Fix it by making sure that all on-disk metadata that we write and read
to/from the metadata image is properly converted.
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
(cherry picked from commit bfc1856029ff6851845de27114fea899bbdbccbe)
commit 2bb826370c12f599fe6cc401fa83a0e7a592f0df
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Apr 9 15:37:00 2018 -0400
tests: don't leave temp files behind after running i_bitmaps
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 4c41e6801fad37fedbbe8feb849eec190b41a733
Author: Eric Sandeen <sandeen@redhat.com>
Date: Mon Apr 9 15:28:12 2018 -0400
e2fsck: warn if checkinterval and broken_system_clock both set
If broken_system_clock is set in e2fsck.conf and this causes
the check interval to be ignored, make that clear to the user:
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda1: ignoring check interval, broken_system_clock set
/dev/sda1: clean, 11/65536 files, 12955/262144 blocks
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
commit bfc1856029ff6851845de27114fea899bbdbccbe
Author: Lukas Czerner <lczerner@redhat.com>
Date: Mon Apr 9 11:58:15 2018 -0400
e2image: fix metadata image handling on big endian systems
Currently e2image metadata image handling and creating is completely
broken on big endian systems. It just does not care about endianness at
all. This was uncovered With addition of i_bitmaps test, which is the
first test that actually tests e2image metadata image.
Fix it by making sure that all on-disk metadata that we write and read
to/from the metadata image is properly converted.
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 635300c774f4c760baf7c9f8891023df66cd12a2
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Apr 7 00:28:49 2018 -0400
libext2fs: add sanity checks for ea_in_inode
An inode containing the value for an extended attribute (aka an
ea_in_inode) must not have the INLINE_DATA flag and must have the
EA_INODE flag set. Enforcing this prevents e2fsck and debugfs crashes
caused by a maliciously crafted file system containing an inode which
has both the EA_INODE and INLINE_DATA flags set, and where that inode
has an extended attribute whose e_value_inum points to itself.
Reported-by: Wen Xu <wen.xu@gatech.edu>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
(cherry picked from commit 9db53e3fec3413572a2240bd374e76353fab9cbe)
commit 23b748563cb6d8c000fd7411bd5a4df96d535ecd
Author: Darrick J. Wong <darrick.wong@oracle.com>
Date: Sun Mar 25 12:01:33 2018 -0700
e2fsck: adjust quota counters when clearing orphaned inodes
If e2fsck encounters a filesystem that supports internal quotas, it is
responsible for adjusting the quota counters if it decides to clear any
orphaned inodes. Therefore, we must read the quota files, adjust the
counters, and write the quota files back out when we are done.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
(cherry picked from commit 7d79b40bb30e5c1c24ee2072b4b104f5927bb330)
commit 346db5ddf222fef3c9a88676e55f2f38527838e4
Author: Andreas Dilger <adilger@dilger.ca>
Date: Thu Mar 29 12:36:54 2018 -0600
filefrag: avoid temporary buffer overflow
If an unknown flag is present in a FIEMAP extent, it is printed as a
hex value into a temporary buffer before adding it to the flags. If
that unknown flag is over 0xfff then it will overflow the temporary
buffer.
Reported-by: Sarah Liu <wei3.liu@intel.com>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10335
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
(cherry picked from commit 17a1f2c1929630e3a79e6b98168d56f96acf2e8b)
commit b46fbf3d52e722d9810dad97a5fa443b280c8a82
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Apr 7 01:12:00 2018 -0400
tests: add new test f_ea_inode_self_ref
Make sure we can handle a maliciously created file system containing
an inode containing an extended attribute whose e_value_inum points
back at itself.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 9db53e3fec3413572a2240bd374e76353fab9cbe
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Apr 7 00:28:49 2018 -0400
libext2fs: add sanity checks for ea_in_inode
An inode containing the value for an extended attribute (aka an
ea_in_inode) must not have the INLINE_DATA flag and must have the
EA_INODE flag set. Enforcing this prevents e2fsck and debugfs crashes
caused by a maliciously crafted file system containing an inode which
has both the EA_INODE and INLINE_DATA flags set, and where that inode
has an extended attribute whose e_value_inum points to itself.
Reported-by: Wen Xu <wen.xu@gatech.edu>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit c52d7eff8c5fb38900e2c702e92f88c6b934c6f2
Author: Ingo Brückl <ib@wupperonline.de>
Date: Sat Mar 31 16:59:48 2018 -0400
tests: don't use "debugfs -f /dev/stdin"
Don't use "debugfs -f /dev/stdin" for portability reasons --- not all
systems have /dev/stdin. Simply dropping "-f /dev/stdin" works just
fine.
Signed-off-by: Ingo Brückl <ib@wupperonline.de>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 79284d3992a11bf6f39fd2c0c606d038b99f4774
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 31 16:38:48 2018 -0400
tests: use mke2fs and debugfs from the build tree
The tests f_bigalloc_badinode and f_bigalloc_orphan_list were not
using the version of mke2fs and debugfs from the build tree, and if
mke2fs and debugfs are not in the user's PATH, these tests would fail.
Fix this.
Reported-by: Somchai Smythe <buraphalinuxserver@gmail.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 7d79b40bb30e5c1c24ee2072b4b104f5927bb330
Author: Darrick J. Wong <darrick.wong@oracle.com>
Date: Sun Mar 25 12:01:33 2018 -0700
e2fsck: adjust quota counters when clearing orphaned inodes
If e2fsck encounters a filesystem that supports internal quotas, it is
responsible for adjusting the quota counters if it decides to clear any
orphaned inodes. Therefore, we must read the quota files, adjust the
counters, and write the quota files back out when we are done.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 17a1f2c1929630e3a79e6b98168d56f96acf2e8b
Author: Andreas Dilger <adilger@dilger.ca>
Date: Thu Mar 29 12:36:54 2018 -0600
filefrag: avoid temporary buffer overflow
If an unknown flag is present in a FIEMAP extent, it is printed as a
hex value into a temporary buffer before adding it to the flags. If
that unknown flag is over 0xfff then it will overflow the temporary
buffer.
Reported-by: Sarah Liu <wei3.liu@intel.com>
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-10335
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 4ec98780067ec292efb64fde2c98833a4ed35ac4
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 24 22:55:14 2018 -0400
Remove debian patches for v1.44.x releases
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit cb5f4b4d1c46a11f65bf52dc5aec13739eb8f143
Merge: 586b4ceb 74892462
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 24 22:53:25 2018 -0400
Merge branch 'maint' into debian-packaging
commit 748924621fdd0e70a191091915fc9724d42e4796
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 24 20:55:05 2018 -0400
Update release notes, etc., for the 1.44.1 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 51ed02bec92431d032d3e5eb0b4b234eef97abc6
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 24 22:26:24 2018 -0400
libext2fs: support operating systems that don't have strnlen()
Someone was trying to build e2fsprogs on MacOS 10.6.8, and ran into
build problems because MacOS didn't have strnlen() support until seven
years ago.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reported-by: Jens Bauer <jens@plustv.dk>
commit 46cf3712b39bc83bb5dbd6bd19ecc21af80d6ac1
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 24 21:44:30 2018 -0400
Add some minor clarifications to chattr's man page
Addresses-Debian-Bug: #890390
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit d7829f0500f543645a4e7499516e6212090721ae
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 24 12:09:09 2018 -0400
debian: add Vcs-* fields to debian packaging
Addresses-Debian-Bug: #887512
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 07d5857e53909257c45f78bf68a08f8fe7f6c250
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 24 11:39:09 2018 -0400
tests: explicitly specify 1k block sizes when creating test file systems
On the Hurd, mke2fs will force the use of 4k block sizes by default
because the Hurd's implemntation of ext2 doesn't support any other
block sizes. This causes spurious test failures. Since these test
are testing e2fsprogs functionality, force the use of 1k block sizes
so the test output matches the expected output.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 63ae5ee05485314e3851ca7f9964e2620e2973fa
Author: Göran Uddeborg <goeran@uddeborg.se>
Date: Sat Mar 24 11:22:57 2018 -0400
po: update sv.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 9d248022a30f12374e7bb591e83183be7a381574
Author: harshads <harshads@google.com>
Date: Fri Mar 23 11:34:05 2018 -0700
e2fsck: delete bad inode fix for bigalloc
While deleting a bad inode in fsck pass2, we should remove clusters
only once. We do it by remembering last released cluster while
deleting clusters one by one.
Signed-off-by: Harshad Shirwadkar <harshads@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 7cc4cf5c7c010a01b38c89065e4ee0465f3692b4
Author: harshads <harshads@google.com>
Date: Fri Mar 23 11:32:49 2018 -0700
debugfs: release clusters only once in release_blocks_proc
While killing file by inode in debugfs (kill_file_by_inode), if
bigalloc feature is turned on, release clusters only once. We do it by
remembering the last released cluster while releasing blocks. We
release a cluster only if it is not already released.
Signed-off-by: Harshad Shirwadkar <harshads@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 6a6393964f045d1d85503f9f4202811bde840875
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Mar 20 11:04:27 2018 -0400
debugfs: read allocation bitmaps more efficiently
It is more efficient to use ext2fs_read_bitmaps() than to read the
inode and block bitmaps separately, since extra seeks.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 2b118575f59880ada77a81ea1bb3c34fe77cff52
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Mar 20 11:01:49 2018 -0400
tests: add new test i_bitmaps
This is a test to make sure e2image and its associated library
routines can correctly read the inode and block allocation bitmaps.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 68192a8f83e008e49ada325f7ec894069d9cc403
Author: Robert Schiele <rschiele@gmail.com>
Date: Tue Mar 20 00:38:48 2018 -0400
util: allow subst to build in cross build environemnt
In a cross build environment we don't get definition of
HAVE_SYS_STAT_H from config.h, therefore we need to define it locally
in that case similar to HAVE_SYS_TIME_H.
Fixes: 7fd537401270 ("misc: add missing declarations on maint")
Signed-off-by: Robert Schiele <rschiele@gmail.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 627901befd76d7d54508919145940147f2c187fe
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Mar 19 18:58:09 2018 -0400
libext2fs: fix reading bitmaps from e2image files
The loop termination code was broken, so that only the first block's
worth of bitmap data was getting read.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reported-by: Kazuya Mio <k-mio@sx.jp.nec.com>
commit 47438fccc19ceddb8a640e861674ff7b1ad04730
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Mar 19 18:23:04 2018 -0400
libext2fs: teach e2image imager to handle bigalloc file systems
Previously, "mke2fs -t ext4 -O bigalloc /tmp/foo.img 4G ;
e2image /tmp/foo.img /tmp/foo.e2i" would result in e2image
dumping core. Fix ext2fs_image_bitmap_write() so it handles
file systems with bigalloc correctly.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 80aa945850c1bf885694035f70a7ecf2dde96704
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Mar 19 18:06:53 2018 -0400
misc: add makefile rules for dumpe2fs.static and e2image.static
These makefile targets are not built by default, but making them
available makes debugging easier.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 8b061a641dff1a0becf645f8e6002de79b997b95
Author: Kazuya Mio <k-mio@sx.jp.nec.com>
Date: Sat Mar 17 14:56:15 2018 -0400
libext2fs: fix ext2fs_open2() error for meta_bg image file
dumpe2fs/debugfs can examine the image file by using the -i option.
However, if meta_bg feature is enabled, dumpe2fs/debugfs cannot open
the image file.
$ dumpe2fs -i test.img
dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open test.img
Couldn't find valid filesystem superblock.
In case of specifying an image file, the location of block group descriptors
is the same as the case of default filesystem regardless of meta_bg feature.
So if EXT2_FLAG_IMAGE_FILE flag is set in ext2fs_open2(),
don't use the meta_bg handling.
Signed-off-by: Kazuya Mio <k-mio@sx.jp.nec.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit a126f79a0eee38762d8e3d110281ae86322de444
Author: Theodore Ts'o <tytso@mit.edu>
Date: Fri Mar 16 11:19:02 2018 -0400
tests: add new test f_bigalloc_orphan_list
This is a regression test for the bugfix found in commit 707599bf:
"e2fsck: release clusters only once in release_inode_blocks"
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 707599bf480195c98e3991fdb6b9d614a0427eef
Author: harshads <harshads@google.com>
Date: Tue Mar 13 16:19:07 2018 -0700
e2fsck: release clusters only once in release_inode_blocks
While releasing inode blocks, if bigalloc feature is turned on,
release clusters only once. We do it by remembering the last released
cluster while iterating through blocks and releasing a cluster only if
it is not already released.
Signed-off-by: Harshad Shirwadkar <harshads@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit e042869209267a331dde4924965d1cfdf9b50c9b
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 10 19:44:37 2018 -0500
misc/fsck: fix potential memory leak on error path
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 1d9ec88df621a74abb2a0430b474cac3c4fc998a
Author: Lukas Czerner <lczerner@redhat.com>
Date: Fri Mar 9 12:28:02 2018 +0100
e2fsck: fix endianness problem when reading htree nodes
Wrong directory block number can be saved in ->previous on big endian
system in parse_int_node(). Fix it by moving the mask out of the endian
conversion.
Fixes: ae9efd05a986 ("e2fsck: 3 level hash tree directory optimization")
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 4d32184d220bc3a56d3630d00a8c696389fe25ee
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 10 16:17:05 2018 -0500
Fix build problems on the Hurd OS
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit b2428898a8b51454b6220d714aaf81d44f22fe6d
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 10 14:29:31 2018 -0500
Fix date for v1.44.0 release notes
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 2c2dd09357968da8cb8e41f4bb910374d9722be0
Author: Theodore Ts'o <tytso@mit.edu>
Date: Wed Mar 7 14:47:46 2018 -0500
Update release notes, etc., for the 1.44.0 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 63c528e9e48324d44767a701062bb3d736c2cb50
Author: Trần Ngọc Quân <vnwildman@gmail.com>
Date: Wed Mar 7 14:23:57 2018 -0500
po: update vi.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit d28d6defa0d0f37677538567a8c1d88351c85c0f
Author: Yuri Chornoivan <yurchor@ukr.net>
Date: Wed Mar 7 14:23:56 2018 -0500
po: update uk.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 2d3212707f899a62676d42f625a9405caec5013c
Author: Sharuzzaman Ahmat Raslan <sharuzzaman@gmail.com>
Date: Wed Mar 7 14:23:56 2018 -0500
po: update ms.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit ec480b9e0f8fd7e87136f926cceb488f7fb3681a
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Wed Mar 7 14:23:56 2018 -0500
po: update fr.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 9b989c5490fadea865086a51f6e81c815dec2fd4
Author: Antonio Ceballos <aceballos@gmail.com>
Date: Wed Mar 7 14:23:56 2018 -0500
po: update es.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit a5a537e1b984bb8abae40d44198bcccaa79e312c
Author: Petr Pisar <petr.pisar@atlas.cz>
Date: Wed Mar 7 14:23:56 2018 -0500
po: update cs.po (from translationproject.org)
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit c8c41d480311e1c0b5b2d587a3ea0799974216fa
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sun Mar 4 16:30:46 2018 -0500
Update release notes, etc., for the 1.44.0-rc2 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 918d9a54fe732709519208245354597807682877
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:23 2018 -0800
tests: test e2fsck's handling of bad symlinks
Add a test which verifies that e2fsck will detect a variety of bad
symlinks, both fast and slow, and with several combinations of
filesystem features including extents, encryption, and inline_data.
There was already a similar test (f_badsymlinks), but it's an old test
that doesn't use any of these newer filesystem features.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 2c733c3f86fa83e2f7b9b5430fade71b11dce6f7
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:22 2018 -0800
e2fsck: require that fast symlinks don't have EXT4_EXTENTS_FL
It doesn't make sense for EXT4_EXTENTS_FL to be set on a fast symlink.
The kernel doesn't set it, and it ignores it if set. Meanwhile, e2fsck
is stricter: it will try to validate the extent tree, which will almost
certainly fail (assuming the symlink is, in fact, a fast symlink).
Make this behavior more explicit by rejecting EXT4_EXTENTS_FL for fast
symlinks, rather than going ahead and trying to validate an extent tree.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 9666fbfbd5d2f6a94566c427c3769ca73d3d01c7
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:21 2018 -0800
e2fsck: validate the targets of extent-based symlinks
e2fsck is validating the target (requiring that it be NUL-terminated at
i_size, or something a bit different for encrypted symlinks) of slow
symlinks that use a traditional block list but not ones that use an
extent tree. As far as I can tell this is simply a bug: there's no
reason for the representation of the block list to affect how the
symlink target is validated. And either way the kernel won't create
symlinks with embedded NULs and will always add a terminating NUL.
Thus, make e2fsck_pass1_check_symlink() start validating the targets of
extent-based symlinks.
Fixes: 7cadc57780f3 ("e2fsck: Support long symlinks which use extents")
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 751efa803bde8b8f150d97e3208a1ce15a9da0bc
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:20 2018 -0800
e2fsck: drop redundant checks of symlink i_size
e2fsck_pass1_check_symlink() verifies that the symlink inode's i_size is
less than the buffer length (60 for fast symlinks, fs->blocksize for
slow symlinks). But it also verifies that len == i_size &&
len < buflen, which already implies i_size < buflen. Thus, remove the
redundant checks of i_size.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 203be6feb53e545bd5972b99713dd1f95c2b2763
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:19 2018 -0800
e2fsck: require i_size == fscrypt_symlink_data.len + 2
e2fsck validates that unencrypted symlinks have their strlen() equal to
i_size. But it skips the equivalent check of i_size ==
fscrypt_symlink_data.len + 2 for encrypted symlinks. Actually, the
encrypted symlink header is redundant with i_size and shouldn't exist.
But it's there, and the kernel does in fact use the length in the header
instead of i_size -- so e2fsck should validate the header.
Thus, remove the exception for encrypted symlinks, so e2fsck will now
require i_size == fscrypt_symlink_data.len + 2. I think the exception
was only there originally because for encrypted fast symlinks we were
calculating the length using strnlen() which was wrong. But that was
fixed by the previous patch.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 22be59d16bdee1748b7d73f8c49dc4525c6cccff
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:18 2018 -0800
e2fsck: validate fscrypt_symlink_data.len for fast symlinks too
Both fast and slow encrypted symlinks are prefixed with the ciphertext
length field (fscrypt_symlink_data.len). But e2fsck was only checking
it for slow symlinks. Start checking it for fast symlinks too. This
matches the kernel handling of encrypted symlinks.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 3a86e7a7c7d9d44d564ebadee134dd981118ba14
Merge: 50c1e18a 0af82798
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat Mar 3 16:39:32 2018 -0500
Merge branch 'maint' into next
commit 0af827988f07386898efdf83271900f91eb507b1
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:17 2018 -0800
e2fsck: validate that fscrypt_symlink_data.len is not too large
Make e2fsck start validating that the ciphertext length stored in the
header of an encrypted symlink target, plus the header itself, is no
larger than a filesystem block. Previously e2fsck only verified that
this size is not exactly equal to a filesystem block. This was
sufficient for unencrypted symlinks, where the "actual length" is
computed using strnlen(), but not for encrypted symlinks; the kernel
also considers encrypted symlinks with too-large ciphertext length to be
invalid.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 6471c19d8edc66ef85c03f83502fc673e7313f74
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:16 2018 -0800
e2fsck: fix reading fscrypt_symlink_data.len
The ciphertext length field stored at the beginning of encrypted symlink
targets is 16-bit. But e2fsck_pass1_check_symlink() is reading it as
32-bit. This was apparently left over from an earlier on-disk format
that was not merged. Fix it.
This bug caused a small proportion of encrypted symlinks with 4092-byte
targets to be considered invalid by e2fsck, but otherwise had no effect.
Fixes: 62ad24802c6e ("e2fsck: handle encrypted directories which are indexed using htree")
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 198a2d0a77d1c33790855c7827da6f1520db103e
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:15 2018 -0800
libext2fs: make sure the system.data xattr gets created
Both the kernel and e2fsck expect that if an inode has inline data, then
it contains a "system.data" xattr -- even if i_size <= 60 so the data
fits entirely in i_block.
But if a symlink of exactly 60 bytes (not counting a NUL terminator) was
created using ext2fs_symlink() and the inline data feature was enabled,
then the symlink inode ended up with inline data but without a
system.data xattr. This is possible because "fast" symlinks store a NUL
terminator but inline data symlinks do not. So 60 bytes is too long for
a real fast symlink, but still short enough to fit the entire target in
i_block as a "slow" symlink using inline data.
Some places use ext2fs_inline_data_init() to ensure the system.data
xattr is created, but the symlink path does not.
Fix this by making ext2fs_inline_data_set() set system.data to an empty
string when i_size <= 60.
Fixes: 54e880b870f7 ("libext2fs: handle inline data in read/write function")
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit c88970f2258459e84f3fbed3b80653b3e8746dfb
Author: Eric Biggers <ebiggers@google.com>
Date: Fri Mar 2 16:59:14 2018 -0800
libext2fs: forbid creating symlinks using entire block
ext2fs_symlink() didn't count the NUL terminator when limiting the
symlink target length to fs->blocksize, so it could create symlinks
using the entire block. Such symlinks are problematic because if
block_size == PAGE_SIZE (as is usually the case), then when following
such a symlink the kernel will truncate the last byte because it needs
to ensure the symlink page is NUL-terminated (see page_get_link()).
Perhaps for that reason, e2fsck considers such symlinks to be invalid
(although only if they use the traditional block list rather than an
extent tree, which seems to be another bug).
Fix this by counting the NUL terminator, thereby decreasing the maximum
accepted symlink target length by 1. Note that this matches the
kernel's behavior in ext4_symlink().
This breaks the test 'f_create_symlinks' which was using debugfs to
create a 1024-byte symlink (not counting the NUL terminator) on a
1024-byte block filesystem. Fix it by removing the leading '/' from the
test's symlink targets so that their lengths are decreased by 1.
Fixes: f01c1a6bce5e ("libext2fs: add the ext2fs_symlink() function")
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 50c1e18ab931d9da9bb8710d161dca0ad80b9f07
Merge: 899425bb eed9d845
Author: Theodore Ts'o <tytso@mit.edu>
Date: Fri Mar 2 18:25:41 2018 -0500
Merge branch 'maint' into next
commit eed9d845e84f6b74ce2d1a475020a17f2131e3d0
Author: Eric Biggers <ebiggers@google.com>
Date: Thu Mar 1 21:21:35 2018 -0800
blkid: fix building e2fsprogs with internal libblkid
Building e2fsprogs with the internal libblkid fails for me with the
following compiler error:
In file included from blkidP.h:27:0,
from dev.c:17:
dev.c: In function ‘blkid_free_dev’:
../../lib/blkid/list.h:149:42: error: ‘intptr_t’ undeclared (first use in this function); did you mean ‘__intptr_t’?
((type *)((char *)(ptr)-(unsigned long)(intptr_t)(&((type *)0)->member)))
The problem is that lib/blkid/list.h is now using 'intptr_t', but
stdint.h is not guaranteed to have been included yet. Include it.
[ Changed to use inttypes.h if it is available and fall back to stdint.h
if it is not available - tytso ]
Fixes: 0a3d8041892c ("AOSP: build mke2fs for windows using android mingw library")
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit e7be7781e43a27321872adeeafdc40d30de6b061
Author: Eric Biggers <ebiggers@google.com>
Date: Thu Mar 1 19:52:57 2018 -0800
e2fsck: remove get_filename_hash() prototype
get_filename_hash() is not defined anywhere, so remove its prototype.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 0b5c918d7885ae65729510600e240f04b8beef4f
Author: Eric Biggers <ebiggers@google.com>
Date: Thu Mar 1 19:52:36 2018 -0800
.gitignore: add cscope files
The .gitignore file for e2fsprogs was ignoring the index files for ctags
but not for cscope. Add cscope to the list.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 4aa098ae611dfb4e4f66905c2b1086182e5efbbd
Author: Eric Biggers <ebiggers@google.com>
Date: Thu Mar 1 19:51:22 2018 -0800
.gitignore: add misc/e4crypt and misc/e4crypt.8
It was forgotten to add these to .gitignore when e4crypt was added.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 2cae256c333a17f8a7c95699cf87aa1dcbc16e3d
Author: Theodore Ts'o <tytso@mit.edu>
Date: Fri Mar 2 14:26:52 2018 -0500
config: update config.{guess,sub}
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 97e4f235b89c80dbef7f2c068da3ee298b73a519
Author: Theodore Ts'o <tytso@mit.edu>
Date: Fri Mar 2 14:14:57 2018 -0500
e2freefrag: fix portability problem for Hurd
Hurd doesn't define PATH_MAX, so define a fallback definition.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 899425bb2a75c8a71736039f17d10f73606b181c
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Feb 27 22:25:04 2018 -0500
Update release notes, etc., for the 1.44.0-rc1 release
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit a9d9ff7ee12e00c9caf977f36665e6c2fd0ce27a
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Feb 27 22:15:54 2018 -0500
libext2fs: declare local functions static to avoid namespace leakage
The functions, xattr_array_update() and space_used() were accidentally
allowed to be declared extern and were thus made available via the
shared library. Fix this.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 60bf373e452bc3ea9573cebb27cbeb4d8536117f
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Feb 27 17:32:27 2018 -0500
Break up RELEASE-NOTES into files in doc/RelNotes
The RELEASE-NOTES file was getting too big as be unweildy. It also
made it hard to have simultaneous releases of older maintenance
releases. So split it up into smaller files in the doc/RelNotes
directory.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit b636e0cb04d6a149809f3356ba50405075d5d3d2
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue Feb 27 01:27:10 2018 -0500
resize2fs: remove bigalloc warning for online resizing
The kernel supports online resizing of bigalloc file systems. There's
no real point to have a scary messaging when doing an online resize of
bigalloc file systems, since all of the heavy lifting is done by the
kernel.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit fbfe156112b9f7d8a105f45900d0fffb7d5003af
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Feb 26 21:54:42 2018 -0500
mke2fs: use io_channel_flush() instead of sync() for sync_kludge
Also add support so that sync_kludge can be set via /etc/mke2fs.conf.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit f5488ffb877713cca25fbfcbb613d32b8d38f85a
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Feb 26 21:19:02 2018 -0500
Clean up util/android_config.h
Remove duplicate #defines and reorganize them to minimize excess
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 220c826f236fd45633d44927f6431d4b58667d01
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Feb 26 20:56:33 2018 -0500
remove AOSP's lib/config.h and update util/android_config.h
While synchronizing with the AOSP e2fsprogs tree, lib/config.h was
accidentally checked in. In the upstream repository, the official
copy of lib/config.h for Android should be stored in
util/android_config.h, since lib/config.h will confuse Unix builds.
This means that when synchronizing with the AOSP tree, changes
lib/config.h need to be reflected in util/android_config.h
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit c19b18f84b67681da7f0b778d25830af67a888f3
Author: Theodore Ts'o <tytso@mit.edu>
Date: Mon Feb 26 13:54:20 2018 -0500
AOSP: use e2fsprogs-defaults for ccflags
From AOSP commit: 2002d7f1fc: Use -Werror in external/e2fsprogs
... which got reverted and reapplied in a confusing way.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
commit 33b80078dbc2294339aa81b752ee3ebf118aaf5b
Author: Jeff Gaston <jeffrygaston@google.com>
Date: Thu Mar 16 15:41:13 2017 -0700
AOSP: Revert "Add "libc" to soong static_executable targets."
This reverts commit b799ad178fa18c2925a283206496d3f5d6e87f35.
It's no longer needed after https://android-review.googlesource.com/c/329298/
Bug: 34722432
Test: lunch aosp_arm-eng && mmma external/e2fsprogs
Change-Id: I4115fe89ef7751364053223be24e7682e66b6b67
From AOSP commit: 34115ec38e86ba3cc17ae7a866e891abf7bd3aeb
commit 25a03337db1617c5d2cfe7c6d8f92b8b90131f8a
Author: Steven Moreland <smoreland@google.com>
Date: Mon Feb 12 15:18:03 2018 -0800
AOSP: mke2fs: Don't require mke2fs.conf on Windows.
This target doesn't exist on Windows.
Fixes the following error:
build/make/core/main.mk:586: warning: Missing required dependency host_cross_mke2fs.conf from module host_cross_mke2fs defined in out/soong/Android-aosp_walleye.mk
Bug: 7456955
Test: above error no longer present
Change-Id: I278e53488ecfc4f9d5e540a70276344af06ad455
From AOSP commit: dd086f6cfbec49e47ae407d9cbbbc374edd2925b
commit ce535b9c670ac4d666ca48aebd5d453045b0a3da
Author: Mark Salyzyn <salyzyn@google.com>
Date: Mon Feb 12 13:17:21 2018 -0800
AOSP: mke2fs: add links for mkfs.ext[234]
LTP tests assume existence of mkfs.ext[234] in order to create
filesystems, so we add the symbolic links.
Test: vts
Bug: 31226527
Bug: 31226662
Bug: 31226379
Bug: 31226047
Bug: 31226376
Bug: 31226714
Bug: 31226122
Bug: 31225634
Bug: 31226069
Bug: 31226031
Bug: 31225881
Bug: 31226562
Bug: 31226411
Bug: 31226410
Bug: 31226028
Bug: 31226509
Bug: 31226253
Bug: 31226404
Bug: 31226353
Bug: 31225624
Bug: 31225677
Bug: 31225191
Change-Id: I039c9e495d11dfc448f7f0de9e519394ed827d7a
From AOSP commit: cca6a5cea983546f08584e74bba271524ce37b11
commit 061b7443ccae2050864b8665c76c9c545cbcf991
Author: Dong Jinguang <dongjinguang@huawei.com>
Date: Fri Dec 29 17:00:37 2017 +0800
AOSP: blkid: sanity check 'end' address must be greater than or equal to 'lable' address.
Avoid a potential out-of-bounds memory access address of label
Test: mma -j8 and boot devices
Change-Id: I155aa4e26f7079f517be3202de0032a86368559d
From AOSP commit: 38324e758b803e99419d24e16a00b32f8ebbf473
![[bug history graph]](https://qa.debian.org/data/bts/graphs/e/e2fsprogs.png){kind=link}