All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: OUPS 2.5.69-bk19 coda-inode.c/slab.c
Date: 27 May 2003 10:23:43 +0100	[thread overview]
Message-ID: <1054027420.1861.1.camel@nalesnik.localhost> (raw)
In-Reply-To: <20030527004322.GA1690@delft.aura.cs.cmu.edu>

On Tue, 2003-05-27 at 01:43, Jan Harkes wrote:
> On Mon, May 26, 2003 at 06:45:40PM +0100, Grzegorz Jaskiewicz wrote:
> > following BUG() is started when coda is included into kernel. I have not
> > tried module, but i bet it will couse the same error.
> 
> Although I don't run the -bkXX releases, as far as I can see this is not
> related to anything in Coda bug, but probably a missing change to slab.c.
> 
> A flag was added to the slabcache to identify reclaimable slabs. I can
> see how this BUG would get triggered if your kernel was linked with an
> old version of slab.o or is missing the SLAB_RECLAIM_ACCOUNT related
> changes in slab.c.
> 
> Maybe "make clean ; make bzImage modules" will fix it?
I am allways doing that in case of problems. So this is not a case, I
bet this is missing patch for slab.c. Becouse this part i showed (along
with mine two debug lines) does not look to good.
 
-- 
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 labs


      reply	other threads:[~2003-05-27  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 17:45 OUPS 2.5.69-bk19 coda-inode.c/slab.c Grzegorz Jaskiewicz
2003-05-27  0:43 ` Jan Harkes
2003-05-27  9:23   ` Grzegorz Jaskiewicz [this message]

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=1054027420.1861.1.camel@nalesnik.localhost \
    --to=gj@pointblue.com.pl \
    --cc=jaharkes@cs.cmu.edu \
    --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 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.