From: Andrew Morton <akpm@zip.com.au>
To: lkml <linux-kernel@vger.kernel.org>,
"ext3-users@redhat.com" <ext3-users@redhat.com>
Subject: ext3-2.4-0.9.16
Date: Thu, 10 Jan 2002 22:00:41 -0800 [thread overview]
Message-ID: <3C3E7F89.AB2F629@zip.com.au> (raw)
A small ext3 update. It fixes a few hard-to-hit but potentially
serious problems. The patch is against 2.4.18-pre3, and is also
applicable to 2.4.17.
http://www.zip.com.au/~akpm/ext3-2.4-0.9.17-2418p3.gz
0.9.17 12 Jan 2002
-------------------
- Cleanup from Manfred Spraul which provides better randomisation of inode
generation numbers.
- A locking fix which prevents possible panics when an application is
using ioctl(FIBMAP) against a loaded filesystem.
- Buffer locking fix for journal descriptor buffers - fixes the
"end_request: buffer-list destroyed" crash which can occur under
heavy VM load.
- Fix a buffer locking problem which could cause corruption if a process
is reading from the underlying block device while journal recovery is
in progress.
-
next reply other threads:[~2002-01-11 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 6:00 Andrew Morton [this message]
2002-01-18 23:10 ` ext3-2.4-0.9.16 Robert Love
2002-01-18 23:26 ` ext3-2.4-0.9.16 Ken Brownfield
2002-01-18 23:40 ` ext3-2.4-0.9.16 Dan Chen
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=3C3E7F89.AB2F629@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 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.