linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bill Huey <billh@gnuppy.monkey.org>,
	John Levon <moz@compsoc.man.ac.uk>,
	linux-mm@kvack.org, "Theodore Y. Ts'o" <tytso@MIT.EDU>,
	linux-kernel@vger.kernel.org
Subject: Re: Rik van Riel's VM patch
Date: Sun, 3 Sep 2000 17:47:01 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0009031743190.1112-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <E13VYF1-0000gN-00@the-village.bc.nu>

On Sun, 3 Sep 2000, Alan Cox wrote:

> > Yes, it kicks butt and it finally (just about) removes the final
> > Linux kernel showstopper for recent kernels. ;-)
> 
> Things like random memory corruption from dropping dirty bits,
> and some of the others are far more serious showstoppers alas

Indeed, there are 4 major issues left in the VM area:

1) system hangs under load with 0 lowmem free (but still
   some high memory free)

   [not much details on this one yet]

2) dirty bits can get lost, try_to_swap_out() and other
   places have a race with the hardware

   [from mm/vmscan.c, line 60 has a race with the /hardware/]
     55         if (pte_young(pte)) {
     56                 /*
     57                  * Transfer the "accessed" bit from the page
     58                  * tables to the global page map.
     59                  */
     60                 set_pte(page_table, pte_mkold(pte));
     61                 SetPageReferenced(page);
     62                 goto out_failed;
     63         }

3) it appears something can corrupt page->count or delete a
   page from the cache while the page is locked

   [tripped up by my VM patch?]

4) the innd data corruption bug

   [anybody?]

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
       -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/		http://www.surriel.com/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2000-09-03 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-02 17:39 John Levon
2000-09-03  0:10 ` Bill Huey
2000-09-03  0:28   ` Byron Stanoszek
2000-09-03  2:14   ` Jeff V. Merkey
2000-09-03 21:38     ` Peter Rival
2000-09-03 11:47   ` Alan Cox
2000-09-03 20:47     ` Rik van Riel [this message]
2000-09-04  1:47       ` Andrey Savochkin

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.21.0009031743190.1112-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=billh@gnuppy.monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=moz@compsoc.man.ac.uk \
    --cc=tytso@MIT.EDU \
    /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