mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Serge Noiraud <serge.noiraud@bull.net>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.15-rc5-rt4 and CONFIG_SLAB=y : structure has no member named `nodeid'
Date: Thu, 05 Jan 2006 06:41:56 -0800	[thread overview]
Message-ID: <1136472116.31011.6.camel@localhost.localdomain> (raw)
In-Reply-To: <200601051112.10762.Serge.Noiraud@bull.net>


Looks like nodeid might just be equal to the cpu now. 

You could try turning off CONFIG_DEBUG_SLAB as a temporary solution. It
looks like the DEBUG define depends on that config option .

Daniel

On Thu, 2006-01-05 at 11:12 +0100, Serge Noiraud wrote:
> mercredi 21 Décembre 2005 10:45, Serge Noiraud wrote/a écrit :
> > Hi,
> > 
> > 	testing on i386, I get the following error :
> > ...
> >   CC      mm/slab.o
> > mm/slab.c: In function `cache_alloc_refill':
> > mm/slab.c:2093: error: structure has no member named `nodeid'
> > mm/slab.c: In function `free_block':
> > mm/slab.c:2239: error: structure has no member named `nodeid'
> > mm/slab.c:2239: error: `node' undeclared (first use in this function)
> > mm/slab.c:2239: error: (Each undeclared identifier is reported only once
> > mm/slab.c:2239: error: for each function it appears in.)
> > make[4]: *** [mm/slab.o] Erreur 1
> > ...
> > 
> > You removed nodeid in the slab struct, but many functions use it.
> > 
> I get the same problem with 2.6.15-rt1
> The following patch suppress the error : I'm not sure it's the good correction.
> perhaps we should supress this DEBUG test ?
> 
> --- linux.orig/mm/slab.c
> +++ linux/mm/slab.c
> @@ -2090,7 +2090,6 @@
>             next = slab_bufctl(slabp)[slabp->free];
>  #if DEBUG
>             slab_bufctl(slabp)[slabp->free] = BUFCTL_FREE;
> -           WARN_ON(numa_node_id() != slabp->nodeid);
>  #endif
>                 slabp->free = next;
>         }
>         check_slabp(cachep, slabp);
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      parent reply	other threads:[~2006-01-05 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21  9:45 Serge Noiraud
2006-01-05 10:12 ` Serge Noiraud
2006-01-05 10:50   ` Serge Noiraud
2006-01-05 14:41   ` Daniel Walker [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=1136472116.31011.6.camel@localhost.localdomain \
    --to=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=serge.noiraud@bull.net \
    /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

all inboxes | Powered by JetHome®