Update for 1.44.0 release.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>

3 files changed, 85 insertions, 7 deletions

diff --git a/htdocs/e2fsprogs-release.html b/htdocs/e2fsprogs-release.html
index 9841ee50b..9418b982f 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.44.0">E2fsprogs 1.44.0 (March 7, 2018)</A>
 <LI><A HREF="#1.43.9">E2fsprogs 1.43.9 (February 8, 2018)</A>
 <LI><A HREF="#1.43.8">E2fsprogs 1.43.8 (January 1, 2018)</A>
 <LI><A HREF="#1.43.7">E2fsprogs 1.43.7 (October 16, 2017)</A>
@@ -122,6 +123,83 @@
 <LI><A HREF="#1.02">E2fsprogs 1.02 (January 16, 1996)</A>
 </UL>
 
+<H2><A NAME="1.44.0">E2fsprogs 1.44.0 (March 7, 2018)</A>
+
+<H3>UI and Features</H3>
+
+<P>E2fsprogs now supports the large_dir (INCOMPAT_LARGEDIR) feature.  This
+feature allows larger directories to be created, both with directory
+sizes over 2GB and and a maximum htree depth of 3 instead of the
+current limit of 2.  These features are needed in order to exceed
+the currently limit of approximately 10M entries in a single
+directory for 4KB blocksize (~100k for 1KB).</P>
+
+<P>E2fsprogs now supports the ea_inode (INCOMPAT_EA_INODE) feature, which
+stores large extended attributes in an external inode instead of a
+single data block.  This is backwards compatible with a Lustre file
+system feature, but it has been extended to support deduplicating
+extended attribute values which are used in multiple inodes.</P>
+
+<P>The metadata_csum feature (RO_COMPAT_METADATA_CSUM) is now enabled by
+default by mke2fs.</P>
+
+<P>The resize2fs program will no longer complain about resizing bigalloc
+file systems as being dangerous when doing an on-line resize (since this
+is purely a kernel feature).</P>
+
+<P>Debugfs's ls command will now print the high bits of the inode's mode
+bits.</P>
+
+<H3>Fixes</H3>
+
+<P>Fixed some potential buffer overrun bugs in the blkid library and in the
+fsck program.</P>
+
+<P>There were some corner cases which tune2fs wouldn't correctly handle
+when operating on a file system which was not cleanly mounted and thus
+required running the journal because it could be modified.  Tune2fs will
+now run the journal before trying to change the superblock, and if the
+file system needs to be checked after the journal has been replayed, it
+will require it before proceeding.  Also if the file system is busy (for
+example, because it is in use by Lustre), but is not present in the
+/proc/mounts or /etc/mtab, tune2fs will not try to replay the journal,
+since this could do real damage if it the file system is being actively
+modified by the kernel.</P>
+
+<P>The libss library (used by debugfs) now supports the version 7 of the
+libreadline shared library.</P>
+
+<P>The e2freefrag program will use the GETFSMAP ioctl if it is available
+and the file system is mounted, so that the free space statistics will
+be more accurate.</P>
+
+<P>The consistency checks for symlinks (especially for encrypted and inline
+data file sytems) in e2fsck are now much more careful/stringent.  Also
+fixed a bug where creating a symlink using ext2fs_symlink() which was
+exactly 60 bytes long when inline data was enabled would result in a
+missing system.data xattr.</P>
+
+
+<H3>Performance, Internal Implementation, Development Support etc.</H3>
+
+<P>Mke2fs now uses io_channel_flush() instead of sync() for the sync_kludge
+feature.</P>
+
+<P>E2fsprogs now uses i_size as the primary way of determining whether a
+symlink is a fast symlink.</P>
+
+<P>Fix various compiler and UBSAN warnings.</P>
+
+<P>Long running test are now skipped with "make check" and only run when
+"make fullcheck".  The test runner will warn when potentially long
+running tests are being run via "make check".</P>
+
+<P>E2fsck is now much faster for bigalloc file systems when scanning
+extents for bigalloc file systems.  (Addresses Google Bug #36886699)</P>
+
+<P>Update Czech, Spanish, French, Malay, and Ukrainian translations.</P>
+
+
 <H2><A NAME="1.43.9">E2fsprogs 1.43.9 (February 8, 2018)</A></H2>
 
 <P>Remove the huge file flag from libe2p (and hence from chattr/lsattr),
diff --git a/htdocs/ext2.html b/htdocs/ext2.html
index 26990f757..d5d21d913 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.43.9 of e2fsprogs is available!</H2>
+<H2>Release 1.44.0 of e2fsprogs is available!</H2>
 
-<P>On February 8, 2018, version 1.43.9 of e2fsprogs was <A
+<P>On March 7, 2018, version 1.44.0 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 38db622dd..aa4bff4f2 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.43.9 of e2fsprogs is
+    <IMG SRC="images/new.gif" ALIGN=LEFT><H2>Release 1.44.0 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.43.9 version as
+    All users of e2fsprogs are urged to upgrade to the 1.44.0 version as
     soon as possible, which can be
-    downloaded from <A HREF="http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.43.9.tar.gz">sourceforge</A>
-    or <A HREF="http://kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.43.9">kernel.org</A>.</P>
+    downloaded from <A HREF="http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.44.0.tar.gz">sourceforge</A>
+    or <A HREF="http://kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.44.0">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.43.8">release notes.</A></P>
+    <A HREF="e2fsprogs-release.html#1.44.0">release notes.</A></P>
 
 
     <ADDRESS>