From: Andrew Morton <akpm@digeo.com>
To: Helge Hafting <helgehaf@aitel.hist.no>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [long]2.5.44-mm3 UP went into unexpected trashing
Date: Thu, 24 Oct 2002 01:17:27 -0700 [thread overview]
Message-ID: <3DB7AC97.D31A3CB2@digeo.com> (raw)
In-Reply-To: 3DB7A80C.7D13C750@digeo.com
Andrew Morton wrote:
>
> Hopefully the rcu fix in -mm4 will cure this.
Oh. It was in -mm3 too. But something went wrong with the
dcache shrinking there.
next prev parent reply other threads:[~2002-10-24 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 7:47 [long]2.5.44-mm3 UP went into unexpected trashing Helge Hafting
2002-10-24 7:58 ` Andrew Morton
2002-10-24 8:17 ` Andrew Morton [this message]
2002-10-24 9:35 ` Dipankar Sarma
2002-10-24 11:45 ` Maneesh Soni
2002-10-24 11:47 ` Ed Tomlinson
2002-10-24 12:38 ` Dipankar Sarma
2002-10-24 15:31 ` Dipankar Sarma
2002-10-24 15:46 ` Dipankar Sarma
2002-10-24 23:35 ` Rusty Russell
2002-10-25 12:27 ` Dipankar Sarma
[not found] ` <3DB98823.67FDBEF3@digeo.com>
[not found] ` <20021025235222.A25786@in.ibm.com>
2002-10-26 15:54 ` Dipankar Sarma
2002-10-29 12:53 ` Ed Tomlinson
2002-10-24 12:46 ` Maneesh Soni
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=3DB7AC97.D31A3CB2@digeo.com \
--to=akpm@digeo.com \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).