All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	ext3-users@redhat.com, ext2-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@zip.com.au>,
	Andreas Dilger <adilger@home.com>
Subject: Re: [Ext2-devel] Re: Ext3-0.9.18 available
Date: Fri, 17 May 2002 13:26:25 +0100	[thread overview]
Message-ID: <ac2tvh$7ko$2@main.gmane.org> (raw)
In-Reply-To: <20020517121746.GA6613@louise.pinerecords.com>; from szepe@pinerecords.com on Fri, May 17, 2002 at 02:17:47PM +0200

Hi,

On Fri, May 17, 2002 at 02:17:47PM +0200, Tomas Szepe wrote:
> > ext3-0.9.18 is now available for 2.4.19-pre8.  Some of the fixes in
> > this release are already in the 2.4.19-pre8, but there are some
> > important new fixes in the patch and users are encouraged to upgrade.
> > This release fixes all known outstanding bug reports.
> 
> Is there at least a remote possibility of the fixes getting ported
> to be included in the linux-2.2 ext3 patch (the latest being 0.0.7a?)?

No, there's no need.  The changes come in several groups:

Performance tweaks:
* Speed up MS_SYNC writes
* speed up fsyncs in non-journaled data modes a little

Config/cosmetic tweaks:
* Set up kjournald to be parented under init properly
* config: ext3 is no longer experimental

Fix bugs introduced at various stages during the 2.4 port:
* don't consider ENOSPC a fatal error when allocating an inode
* fix over-zealous ext3 complaint about locked buffers
* fix O_SYNC
* fix tiny race where a buffer could be written to disk too soon

Fix bugs arising from changes made elsewhere during 2.4:
* fix i_blocks getting inconsistent after disk full
* fix "dump corrupts filesystems" core VFS bug
* fix very rare buffer leak

Fix a bug in the LVM interaction (code isn't present in 2.2):
* fix LVM snapshot deadlock

None of the bug-fixes apply to the 2.2 version of the code.

Cheers,
 Stephen

      parent reply	other threads:[~2002-05-17 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 16:56 Ext3-0.9.18 available Stephen C. Tweedie
2002-05-17 12:17 ` Tomas Szepe
2002-05-17 12:26   ` [Ext2-devel] " Stephen C. Tweedie
2002-05-18  0:35     ` Mike Fedyk
2002-05-18  5:37       ` Andreas Dilger
2002-05-17 12:26   ` Stephen C. Tweedie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ac2tvh$7ko$2@main.gmane.org' \
    --to=sct@redhat.com \
    --cc=adilger@home.com \
    --cc=akpm@zip.com.au \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=ext3-users@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szepe@pinerecords.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.