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 [thread overview]
Message-ID: <3C0B12C5.F8F05016@zip.com.au> (raw)
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.
next reply other threads:[~2001-12-03 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 5:51 Andrew Morton [this message]
2001-12-05 12:32 ` ext3-0.9.16 against linux-2.4.17-pre2 Florian Lohoff
2001-12-05 12:36 ` Mike Fedyk
2001-12-05 12:37 ` Florian Lohoff
2001-12-05 23:42 ` Robert Love
2001-12-06 8:30 ` 2.4.17-pre2+ext3-0.9.16+anton's cache aligned smp Yusuf Goolamabbas
2001-12-06 8:39 ` Jens Axboe
2001-12-06 8:45 ` Andrew Morton
2001-12-06 13:02 ` Anton Blanchard
2001-12-07 15:27 ` Daniel Phillips
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=3C0B12C5.F8F05016@zip.com.au \
--to=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox