From: Andrew Morton <akpm@zip.com.au>
To: lkml <linux-kernel@vger.kernel.org>,
"ext3-users@redhat.com" <ext3-users@redhat.com>
Subject: ext3-0.9.15 against linux-2.4.14
Date: Tue, 06 Nov 2001 01:20:44 -0800 [thread overview]
Message-ID: <3BE7AB6C.97749631@zip.com.au> (raw)
Download details and documentation are at
http://www.uow.edu.au/~andrewm/linux/ext3/
Changes since ext3-0.9.13 (which was against linux-2.4.13):
- Fixed a null-pointer dereference oops which could hit on
SMP machines. This fix was applied to 2.4.12-ac6, but the
oops has never been reported against -ac kernels.
- Large amounts of developer debug code has been removed. This
will now be maintained separately.
- There is an interaction failure between ext3 and the current
Extended Attributes and Access Control Lists patch which leads
to crashes under heavy load on SMP. This is possibly due to
a subtle API change between ext3 in 2.2 and 2.4 kernels (ie: I
broke it). On the to-do list.
- For a long time, the ext3 patch has used a semaphore in the core
kernel to prevent concurrent pagein and truncate of the same
file. This was to prevent a race wherein the paging-in task
would wake up after the truncate and would instantiate a page
in the process's page tables which had attached buffers. This
leads to a BUG() if the swapout code tries to swap the page out.
This semaphore has been removed. The swapout code has been altered
to simply detect and ignore these pages.
This is an incredibly obscure and hard-to-hit situation. The testcase
which used to trigger it can no longer do so. So if anyone sees the
message "try_to_swap_out: page has buffers!", please shout out.
There are no plans to remove this semaphore from -ac kernels,
unless Alan wants it that way.
-
next reply other threads:[~2001-11-06 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 9:20 Andrew Morton [this message]
2001-11-06 9:42 ` ext3-0.9.15 against linux-2.4.14 Alan Cox
2001-11-06 18:09 ` Steven N. Hirsch
2001-11-06 18:49 ` Andrew Morton
2001-11-07 0:31 ` Stephen Tweedie
2001-11-07 17:59 ` Andrew Morton
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=3BE7AB6C.97749631@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.