From: Rik van Riel <riel@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-mm@kvack.org, "Stephen C. Tweedie" <sct@redhat.com>,
Andrea Arcangeli <andrea@suse.de>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: filemap.c SMP bug in 2.4.0-test*
Date: Tue, 15 Aug 2000 23:46:22 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0008152344500.3400-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.10.10008151938240.3600-100000@penguin.transmeta.com>
On Tue, 15 Aug 2000, Linus Torvalds wrote:
> On Tue, 15 Aug 2000, Rik van Riel wrote:
> >
> > The debugging check (in mm/swap.c::lru_cache_add(), line 232)
> > checks if the page which is to be added to the page lists is
> > already on one of the lists. In case it is, a nice backtrace
> > follows...
>
> Why do you think your "PageActive()"/"PageInactiveDirty()"/
> "PageInactiveClean()" tests are right?
>
> I don't see any reason to assume that you just don't clear the flags
> correctly.
>
> In fact, if this bug really existed in the standard kernel, you'd see
> machines locking up left and right. Adding a page to a the LRU list when
> it already is on the LRU list would cause immediate and severe list
> corruption. It wouldn't just go silently in the night, it would _scream_.
>
> I would suggest that you add something like DEBUG_ADD_PAGE to
> __free_pages_ok(), and see if somebody frees the page without
> clearing the flags. Sounds like a bug in your code.
This test is in _all_ places where pages are added or
removed from the list and in __free_pages_ok().
The only place where I'm hitting the bug is in
lru_cache_add.
OTOH, I wouldn't mind it if you were to take a look
at my code and potted the bug ;))
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/
next prev parent reply other threads:[~2000-08-16 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 22:10 Rik van Riel
2000-08-16 2:43 ` Linus Torvalds
2000-08-16 2:46 ` Rik van Riel [this message]
2000-08-16 3:26 ` Linus Torvalds
2000-08-16 3:40 ` Rik van Riel
2000-08-16 4:09 ` Rik van Riel
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.0008152344500.3400-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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