mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: maneesh@in.ibm.com, Dipankar Sarma <dipankar@in.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [long]2.5.44-mm3 UP went into unexpected trashing
Date: Thu, 24 Oct 2002 07:47:39 -0400	[thread overview]
Message-ID: <20021024114740.78FD37CD3@oscar.casa.dyndns.org> (raw)
In-Reply-To: <20021024171528.D5311@in.ibm.com>

Maneesh Soni wrote:

> On Thu, Oct 24, 2002 at 08:22:07AM +0000, Andrew Morton wrote:
>> 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.
> 
> Backing out larger-cpu-masks.patch fixes this in -mm3 so, -mm4 should not
> give this problem. Basically callbacks are not getting processed due to
> incorrect rcu_cpu_mask.

Would this affect UP systems?  Had the dentry leak on a UP box with 512m 
memory.  About 400m ended up in unfreeable dentries...

Ed Tomlinson

  reply	other threads:[~2002-10-24 11:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24  7:47 Helge Hafting
2002-10-24  7:58 ` Andrew Morton
2002-10-24  8:17   ` Andrew Morton
2002-10-24  9:35     ` Dipankar Sarma
2002-10-24 11:45     ` Maneesh Soni
2002-10-24 11:47       ` Ed Tomlinson [this message]
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=20021024114740.78FD37CD3@oscar.casa.dyndns.org \
    --to=tomlins@cam.org \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.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

Powered by JetHome