[lkml]   [1998]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectProgress! was: Re: Yet more VM writable swap-cached pages

On Thu, 9 Jul 1998 18:47:10 +0100 (BST), Ganesh Sittampalam
<> said:

> Just after that last e-mail, I got a flood of them.
> Jul 9 18:27:30 munchkin kernel: VM: Found a writable swap-cached page!
> Jul 9 18:27:30 munchkin kernel: pte 6a8042, vma flags 00000070, page
> flags 0000028c, count 2
> Jul 9 18:27:30 munchkin kernel: page=c0206f80@0017da00, found=c0206f80,
> count=3


vma flags represent a private vma with read/write/exec-privilege but
with no rwe currently enabled. Page flags are normal for a resident
swap-cached anonymous page with no IO in flight. The page count, 2, is
also normal for a cached anonymous page. The pte, 6a8042, is not normal
at all. It is marked non-present (the lowest bit is clear) but
_PAGE_PROTNONE. That changes everything.

Thanks --- this tells us exactly what has gone wrong, I think.
Something, somewhere, (electric fence, perhaps?) has set up a region of
memory with no access allowed. There is a page mapped, but it is not
visible to the process: somebody has done an mprotect() to eliminate the
visibility of the page. That clears the _PAGE_PRESENT bit on the pte
but keeps the _PAGE_PROTNONE bit set, and _PAGE_PROTNONE is an alias for
_PAGE_RW!! That's the trouble: the pte_write() test to see if a page is
writable tests the _PAGE_RW bit but fails to first of all check whether
or not _PAGE_PRESENT is set in the first place.

I've just tried to reproduce this with the program at the end, which
creates page of local memory, allows it to be swapped out, then pages it
in and marks it PROT_NONE. I got a slightly different end result,
exactly the same, on two attempts out of two:

swap_free: Trying to free nonexistent swap-page

which also quite possibly results from the swap cache code seeing this
page as writable when it is not. Anyway, it is now clear that we can
reproduce some rather undesirable behaviour using PROT_NONE, and the pte
trace from your own report also indicates that it may be the source of
your own problems.

I _think_ that on Intel we can fix much of this by correcting the macro

extern inline int pte_write(pte_t pte) { return pte_val(pte) & _PAGE_RW; }

to check for (_PAGE_RW && !_PAGE_PRESENT). I'm not entirely sure yet
that this will be the end of it; tomorrow I'll have a dig around to see
if I can find any other nasties which might trip us up here. What are
the implications for other architectures which organise their ptes


Run this. When it suspends itself, force it out to swap somehow then
bring the test program back with "%" at the shell. It will suspend
itself again; at this point, the page should back in the swap cache and
protected PROT_NONE. Things now go wrong.


* Create a page of prot-none memory

#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <sys/mman.h>

void try(const char *why, int error)
if (!error)

int main(void)
int pagesize = getpagesize();
char *page;
volatile char a;

try ("malloc", (page = malloc(2*pagesize)) == NULL);

/* Round up to the next page boundary */
page = (char *) (((unsigned long) page + pagesize-1) & ~(pagesize-1));

/* Make a private page... */
*page = 0;

/* Give it a chance to get swapped out... */
kill (getpid(), SIGSTOP);

/* Swap it back in (leaving it swap-cached of course!)... */
a = *page;

/* ... and map it prot-none. */
try ("mprotect", mprotect (page, pagesize, PROT_NONE));

/* Now, wait for the damage. */
kill (getpid(), SIGSTOP);

return 0;

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to

 \ /
  Last update: 2005-03-22 13:43    [W:0.164 / U:0.676 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site