public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Theodore Ts'o" <tytso@valinux.com>
Cc: Stephen Tweedie <sct@redhat.com>, linux-kernel@vger.kernel.org
Subject: Two VM problems for the 2.4 TODO list
Date: Mon, 4 Sep 2000 17:07:39 +0100	[thread overview]
Message-ID: <20000904170739.I12913@redhat.com> (raw)

Hi Ted,

To be fixed for 2.4:

1) Non-atomic pte updates

   The page aging code and mprotect both modify existing ptes
   non-atomically.  That can stomp on the VM hardware on other CPUs
   setting the dirty bit on mmaped pages when using threads.  2.2 is
   vulnerable too.

2) RSS locking

   swapout holds the page_table_lock while swapping, and adjusts the
   mm->rss while holding that lock.  Other places in the mm are not 
   so careful about holding the lock, so rss (which is not an
   atomic_t) can be corrupted.

--Stephen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-09-04 16:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20000904170739.I12913@redhat.com \
    --to=sct@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@valinux.com \
    /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