linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steven N. Hirsch" <shirsch@adelphia.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"ext3-users@redhat.com" <ext3-users@redhat.com>
Subject: Re: ext3-0.9.15 against linux-2.4.14
Date: Tue, 6 Nov 2001 13:09:42 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0111061305540.8366-100000@atx.fast.net> (raw)
In-Reply-To: <3BE7AB6C.97749631@zip.com.au>

On Tue, 6 Nov 2001, Andrew Morton wrote:

> 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):
> 
> - 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.

Andrew,

I have been getting thousands of these when the system was under heavy 
load, but didn't realize it was from the ext3 code!  I'm using Linus's 
2.4.14-pre7 + ext3 patch from Neil Brown's site (the latter is identified 
as "ZeroNineFourteen".)  Would you like me to upgrade kernel and patch?

Steve



  parent reply	other threads:[~2001-11-06 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06  9:20 ext3-0.9.15 against linux-2.4.14 Andrew Morton
2001-11-06  9:42 ` Alan Cox
2001-11-06 18:09 ` Steven N. Hirsch [this message]
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=Pine.LNX.4.33.0111061305540.8366-100000@atx.fast.net \
    --to=shirsch@adelphia.net \
    --cc=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;
as well as URLs for NNTP newsgroup(s).