[LWN Logo]
[LWN.net]
From:	 Andrew Morton <akpm@zip.com.au>
To:	 "ext3-users@redhat.com" <ext3-users@redhat.com>,
	 lkml <linux-kernel@vger.kernel.org>
Subject: ext3-0.9.16 against linux-2.4.17-pre2
Date:	 Sun, 02 Dec 2001 21:51:01 -0800

An ext3 update which also applies to linux-2.4.16 is available at

	http://www.zip.com.au/~akpm/linux/ext3/

Quite a lot of miscellany here.  It would be appreciated if interested
parties could please test it in preparation for sending upstream.  Thanks.

Changelog:


- Merged several ext2 sync-up patches from Christoph Hellwig

- Drop the big kernel lock across the call to block_prepare_write.
  This was causing excessive contention on large SMP machines.  Thanks
  to Anton ("dbench") Blanchard for finding this.

- Fixed a couple of potential kmap leaks on error paths.

  There is some question whether the core kernel should be changed so
  that this is not necessary, but it is right for current kernels.

- Fixed bugs concerning the use of bit operations on 32 bit quantities,
  which could cause problems on 64-bit hardware.  Thanks davem.

- Fix failure to return EFBIG when an attempt is made to lengthen an
  ext3 file to more than the maximum file size via ftruncate().

- Current ext3 can cause an assertion failure and take down the machine
  when an I/O error is encountered while mapping journal blocks in
  preparation for writing to the journal.  Fix from Stephen turns the
  filesystem readonly when this occurs.

- ext3 is presently marking data dirty itself, which defeats the core
  kernel's dirty buffer balancing.  Take that out and let the generic
  layer mark the buffers dirty.

  This change, along with core kernel changes in 2.4.17-pre2 can
  potentially reduce system congestion under heavy write loads.

- Update Documentation/Changes to reflect requirement for e2fsprogs
  version (1.25)

- Update Documentation/Locking to describe the two address_space
  methods which ext3 introduced.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/