summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2024-05-21 00:04:07 -0400
committerTheodore Ts'o <tytso@mit.edu>2024-05-21 00:04:07 -0400
commitbab42d82be094230d1e1bf495e808fce2e1f8dc5 (patch)
tree540582644134298808772ca81c6b4a93674e18c9
parentc86d21c2bded6494f4a3d4b84c113b03da2fea9a (diff)
downloade2fsprogs-web.tar.gz
Update for the 1.47.1 releaseweb
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
-rw-r--r--htdocs/e2fsprogs-release.html186
-rw-r--r--htdocs/ext2.html4
-rw-r--r--htdocs/index.html10
3 files changed, 192 insertions, 8 deletions
diff --git a/htdocs/e2fsprogs-release.html b/htdocs/e2fsprogs-release.html
index 16c30d669..a215e2a28 100644
--- a/htdocs/e2fsprogs-release.html
+++ b/htdocs/e2fsprogs-release.html
@@ -30,6 +30,7 @@
<H2>Release notes for the e2fsprogs package</H2>
<UL>
+<LI><A HREF="#1.47.1">E2fsprogs 1.47.1 (May 20, 2024)</A>
<LI><A HREF="#1.47.0">E2fsprogs 1.47.0 (February 5, 2023)</A>
<LI><A HREF="#1.46.6">E2fsprogs 1.46.6 (February 1, 2023)</A>
<LI><A HREF="#1.46.5">E2fsprogs 1.46.5 (December 30, 2021)</A>
@@ -145,7 +146,190 @@
<LI><A HREF="#1.02">E2fsprogs 1.02 (January 16, 1996)</A>
</UL>
-<H2><A NAME="#1.47.0">E2fsprogs 1.47.0 (February 5, 2023)</A></H2>
+<H2><A NAME="1.47.1">E2fsprogs 1.47.1 (May 20, 2024)</A></H2>
+
+<H3>UI and Features</H3>
+
+<P>Add post-2038 handling when e2fsprogs is compiled on a system with a
+64-bit time_t.</P>
+
+<P>Mke2fs -d can now support an input tar file if the libarchive library is
+available.</P>
+
+<P>Add a udev rule which inhibits ext4 file systems from being automounted
+by udisks. This avoid security issues from exposing potentially
+maliciously fuzzed file systems from being mounted without being
+inspected using fsck first. Distributions can of course override this
+feature inhibition, but then they get to own the security vulnerability
+liability. Upstream ext4 file system developers are putting
+distributions on notice that blindly automounting file systems from
+(potentially) USB thumb drives which clueless users may have picked up
+in a parking lot is a ***bad*** idea, no matter what clueless enterprise
+Linux product managers might think.</P>
+
+<P>The debugfs 'hash' command will use the hash seed and algorithm from the
+superblock if debugfs has a file system open, instead of requiring the
+user to specify those parameters explicitly as options to the hash
+command. Also add a hash -v option which prints the hash parameters so
+the user knows what parameters were used when calculating the hash for
+the filename.</P>
+
+<P>Teach mke2fs a new extended options, root_perms, which overrides the
+permissions for the root directory for the new file system.</P>
+
+<H3>Fixes</H3>
+
+<P>When various e2fsprogs are replaying the journal (tune2fs, fuse2fs,
+e2fsck, etc.) save any error indicator in the superblock, so it can be
+restored afterwards. Most of the time (at least with modern kernels) if
+file system corruptions are discovered, the superblock update is
+journalled. However, if the journal is aborted or the journal commit
+fails, the error code might only be written in the superblock, so we
+need to save it so that a subsequent fsck can repair the file system
+after the journal replay.</P>
+
+<P>When mke2fs was creating a file system with the orphan file inode, it
+tries to read and truncate the orphan inode before it has been
+initialized. If there is an inode from a previous file system located
+there (as opposed to a all zeroes inode table block caused by a discard
+of the flash device or a newly created cloud block device or fille
+image), it can fail with bad checksum error, aborting the mke2fs
+operation. Fix this in ext2fs_create_orphan_file() not trying to
+truncate the orphan file if it is newly allocated (which will always be
+the case when mke2fs calls this library function).</P>
+
+<P>In the case where e2fsck comes across an orphan file which is empty but
+the orphan_present feature is set, in preen mode, e2fsck will now clear
+the orphan_present feature flag silently.</P>
+
+<P>E2fsck will now perform more consistency checks on EA (extended
+attribute value) inodes.</P>
+
+<P>Fix a big where e2fsck could potentially leak an acl block when
+releasing an orphan inode.</P>
+
+<P>Avoid a divide by zero crash in libext2fs if the container
+infrastructure, such as lxcfs, reports that the system has zero CPU's
+via sysconf(_SC_NPROCESSORS_CONF).</P>
+
+<P>When resize2fs is performing an online resize, it's possible for reading
+the superblock can race with a kernel modifying the superblock with the
+checksum being invalid and causing the resize to fail with an bad
+superblock checksum in the buffer cache. Have resize2fs open the file
+system using O_DIRECT to avoid the superblock with an invalid checksum.</P>
+
+<P>Fix a bug where a checksum failure in an htree directory can cause
+e2fsck's preen mode to abort unnecessarily.</P>
+
+<P>Fix e2fsck's handling of an invalid symlink in an inline_data directory.</P>
+
+<P>Fix e4crypt from issuing a spurious "success" error message when trying
+to set a policy on a non-directory.</P>
+
+<P>Fix a potential infinite loop in debugfs's logdump command in some edge
+cases.</P>
+
+<P>Fix e2fsck to correctly update quota usage after optimizing directories
+or deleting corrupted inodes.</P>
+
+<P>Fix fuse2fs so that directories are created with the correct permissions
+instead of having the other and group write permissions masked off.</P>
+
+<P>Fix a potential e2fsck divide by zero crash caused by a maliciously
+fuzzed file system.</P>
+
+<P>Fix dumpe2fs to report free block ranges correctly for bigalloc file
+systems.</P>
+
+<P>Fix resize2fs where resizing a bigalloc file system can result in the
+free cluster count in the last block group and the total free clusters
+count to be incorrect.</P>
+
+<P>Avoid spurious e2scrub failures caused by trying to scrub file syustems
+that do not have the journal enabled, and by aborting scrub runs while
+upgrading the e2fsprogs package on Debian/Ubuntu.</P>
+
+<P>Teach tune2fs to detect a file system which is mounted but is not
+mentioned in the mount namespace where tune2fs is run by treating a
+block device which is busy as if it is mounted.</P>
+
+<P>If tune2fs can't find the mountpoint for a file system which is
+apparently mounted (perhaps because it's not present in the current
+mount namespace) when attempting to set the label or UUID in the
+superblock, fall back to the old method of modifying block device and
+silence printing any error messages.</P>
+
+<P>If both the primary superblock and first block group's backup superblock
+are corrupted, e2fsck will now try additional backup superblocks if they
+are available.</P>
+
+<P>Avoid mke2fs from creating an invalid file system with an insufficient
+number of inodes when creating a file system which is very small (100k),
+a block size of 1k, and an inode size of 256 bytes.</P>
+
+<P>Fix a potential deadlock caused by e2fsck being run in Direct I/O mode
+with the threading optimization enabled.</P>
+
+<P>Fix e2scrub when the "systemctl" package is installed instead of
+systemd. (Addresses Debian Bug #1070107)</P>
+
+<P>Fixed/improved various Debian packaging issues.</P>
+
+<P>Update and clarify various man pages. (Addresses Debian Bugs #1038286,
+#1041115)</P>
+
+
+<H3>Performance, Internal Implementation, Development Support etc.</H3>
+
+<P>Add support for SOURCE_DATE_EPOCH environment variable per the
+specification https://reproducible-builds.org/specs/source-date-epoch</P>
+
+<P>Improve resize2fs's performance by eliminating extra cache flushes.</P>
+
+<P>Improve mke2fs's performance when zeroing a large number of inode table
+blocks (when lazy inode table initialization is not enabled) by batching
+calls to ext2fs_zero_blocks.</P>
+
+<P>Use a safe_getenv function for all calls to fetch the environment
+variable in libext2fs.</P>
+
+<P>Fix a massive buffer overrun bug in ext2fs_image_super_read(). This
+function isn't actually used by e2image, and it's unlikely that there
+are any users of this function since the most common way the e2image
+file is read is via ext2fs_openfs() with the EXT2_FLAG_IMAGE_FILE, which
+doesn't actually use ext2fs_image_super_read().</P>
+
+<P>Add support for building fuse2fs using Fuse V3.</P>
+
+<P>Use FORTIFY_SOURCE=3 when hardening is enabled for more protection.</P>
+
+<P>Add support for continuous integration tests using Github Actions.</P>
+
+<P>Fix Windows-specific portability bugs to allow mke2fs to create a file
+system in a file which doesn't yet exist and to support file systems
+larger than 2GB.</P>
+
+<P>Fix a FreeBSD 14 build failure caused by changing the function signature
+of qsort_r() to be aligned with the POSIX and glibc definition of
+qsort_r().</P>
+
+<P>Fix various portability issues for the Linux 32-bit musl C library,
+GNU/Hurd and Android. (Addresses Debian Bug: #1056145)</P>
+
+<P>Fix various portability problems in the regression test suite.</P>
+
+<P>Fix various sanitizer, static code analysis, and compiler warnings.</P>
+
+<P>Synchronized changes from Android's AOSP e2fsprogs tree.</P>
+
+<P>Updated config.guess and config.sub with newer versions from the FSF.</P>
+
+<P>Add Romainian translation.</P>
+
+<P>Update Chinese, Czech, French, Malay, Polish, Swedish, and Ukrainian
+translations.</P>
+
+<H2><A NAME="1.47.0">E2fsprogs 1.47.0 (February 5, 2023)</A></H2>
<H3>UI and Features</H3>
diff --git a/htdocs/ext2.html b/htdocs/ext2.html
index a28a9c430..4623cbe12 100644
--- a/htdocs/ext2.html
+++ b/htdocs/ext2.html
@@ -28,9 +28,9 @@
<!-- Begin actual content -->
<IMG SRC="../images/new.gif" ALIGN=LEFT>
-<H2>Release 1.47.0 of e2fsprogs is available!</H2>
+<H2>Release 1.47.1 of e2fsprogs is available!</H2>
-<P>On February 5, 2023, version 1.47.0 of e2fsprogs was <A
+<P>On May 20, 2024, version 1.47.1 of e2fsprogs was <A
HREF="http://e2fsprogs.sourceforge.net">announced</A>.</P>
<H2>Ext2fs Utilities</H2>
diff --git a/htdocs/index.html b/htdocs/index.html
index b34b750b4..287e56263 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -34,18 +34,18 @@
<A HREF="http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html">here</A>.</P>
- <IMG SRC="images/new.gif" ALIGN=LEFT><H2>Release 1.47.0 of e2fsprogs is
+ <IMG SRC="images/new.gif" ALIGN=LEFT><H2>Release 1.47.1 of e2fsprogs is
available!</H2>
<P>I am happy to announce a new release of the e2fsprogs distribution.
- All users of e2fsprogs are urged to upgrade to the 1.47.0 version as
+ All users of e2fsprogs are urged to upgrade to the 1.47.1 version as
soon as possible, which can be
- downloaded from <A HREF="http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.47.0.tar.gz">sourceforge</A>
- or <A HREF="http://kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.47.0">kernel.org</A>.</P>
+ downloaded from <A HREF="http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.47.1.tar.gz">sourceforge</A>
+ or <A HREF="http://kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.47.1">kernel.org</A>.</P>
<P>This release contains a number of bug fixes and enhancements over
the previous releases. For more details, see the
- <A HREF="e2fsprogs-release.html#1.47.0">release notes.</A></P>
+ <A HREF="e2fsprogs-release.html#1.47.1">release notes.</A></P>
<ADDRESS>