From: Andrew Morton <akpm@zip.com.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: 2.4.10pre11 vm rewrite fixes for mainline inclusion and testing
Date: Wed, 19 Sep 2001 22:58:15 -0700 [thread overview]
Message-ID: <3BA98577.3F0A3D5A@zip.com.au> (raw)
In-Reply-To: <20010918224317.E720@athlon.random>
With this patch against -pre12 the BUG()s in shrink_cache()
go away.
--- linux-2.4.10-pre12/mm/vmscan.c Wed Sep 19 20:47:21 2001
+++ linux-akpm/mm/vmscan.c Wed Sep 19 22:49:48 2001
@@ -435,15 +435,20 @@ static int shrink_cache(struct list_head
if (try_to_free_buffers(page, gfp_mask)) {
if (!page->mapping) {
- UnlockPage(page);
-
/*
* Account we successfully freed a page
* of buffer cache.
*/
atomic_dec(&buffermem_pages);
+ /*
+ * We must not allow an anon page
+ * with no buffers to be visible on
+ * the LRU, so we unlock the page after
+ * taking the lru lock
+ */
spin_lock(&pagemap_lru_lock);
+ UnlockPage(page);
__lru_cache_del(page);
/* effectively free the page here */
With this patch applied I've had three total system lockups with
the usual workload. No diagnostics, no interrupts, NMI watchdog
doesn't catch it. Nice. This is not related to networking; I
wasn't able to do much network stress testing because the
darn APIC bug kept biting me. Grumble.
I'll try -pre9.
next prev parent reply other threads:[~2001-09-20 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 20:43 2.4.10pre11 vm rewrite fixes for mainline inclusion and testing Andrea Arcangeli
2001-09-18 19:29 ` Marcelo Tosatti
2001-09-18 19:39 ` Marcelo Tosatti
2001-09-18 21:11 ` Andrea Arcangeli
2001-09-18 21:26 ` Andrea Arcangeli
2001-09-19 6:21 ` Andrew Morton
2001-09-20 5:58 ` Andrew Morton [this message]
2001-09-20 6:11 ` Andrea Arcangeli
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=3BA98577.3F0A3D5A@zip.com.au \
--to=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.