mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Ravikiran G Thirumalai" <kiran@scalex86.org>
Cc: "Andrew Morton" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, "Andi Kleen" <ak@muc.de>,
	"Jan Beulich" <jbeulich@novell.com>,
	"Alok Kataria" <alok.kataria@calsoftinc.com>
Subject: Re: mm snapshot broken-out-2006-08-08-00-59.tar.gz uploaded
Date: Wed, 9 Aug 2006 15:21:22 +0200	[thread overview]
Message-ID: <6bffcb0e0608090621q488eada3h1edae21e94e6997f@mail.gmail.com> (raw)
In-Reply-To: <20060809062159.GA3829@localhost.localdomain>

Hi,

On 09/08/06, Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
> On Tue, Aug 08, 2006 at 04:42:10PM -0700, Andrew Morton wrote:
> > On Wed, 9 Aug 2006 00:11:38 +0200
> > "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com> wrote:
> >
> > ah-hah, thanks.  The oopsing statement was added by
> > slab-fix-lockdep-warnings.patch.
> >
> > I guess we can fix this by whacking another #ifdef CONFIG_NUMA in there but
> > I don't think that's how we want to address this.
> >
> > We've been moving towards making the NUMA slab code work OK in a non-NUMA
> > build by setting the NUMA-specific fields to NULL and simply blowing a few
> > cycles at runtime to avoid many tens of ifdefs (it's that bad).
> >
> > Here, we should have had either l3==NULL or l3->alien==NULL, but that has
> > been violated, hence the crash.
> > Kiran, could you take a look please?  The 0x01020304 is interesting...
>
> Eeesh, because on SMP,  alloc_alien_cache returns 0x01020304 instead of
> NULL, And it returns 0x01020304 because CPU_UP_PREPARE fails if
> alloc_alien_cache returns NULL.  NUMA and non NUMA slab should be able to
> work even without alien caches, currently that doesn't seem to be the case.
> We are working on that.  In the meanwhile, the following patch should
> fix the oops due to locdep annotation.
>
> Thanks,
> Kiran
>
> Fix oops due to alien cache locdep annotation on non NUMA configurations.
> A plain alien != NULL won't work as l3->alien is initialized with
> 0x01020304ul

Bug fixed, thanks.

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

  reply	other threads:[~2006-08-09 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200608080800.k7880noU028915@shell0.pdx.osdl.net>
2006-08-08 20:29 ` Michal Piotrowski
2006-08-08 21:05   ` Andrew Morton
2006-08-08 21:19     ` Michal Piotrowski
2006-08-08 21:37       ` Andrew Morton
2006-08-08 22:11         ` Michal Piotrowski
2006-08-08 23:24           ` Michal Piotrowski
2006-08-08 23:42           ` Andrew Morton
2006-08-09  0:01             ` Michal Piotrowski
2006-08-09  6:21             ` Ravikiran G Thirumalai
2006-08-09 13:21               ` Michal Piotrowski [this message]
2006-08-09  1:43           ` Andi Kleen
2006-08-09 12:49             ` Michal Piotrowski
2006-08-09  1:42     ` Andi Kleen
2006-08-09 14:20 ` Michal Piotrowski
2006-08-09 22:44   ` Michal Piotrowski
2006-08-10  6:35     ` Jens Axboe
2006-08-10 13:06       ` Michal Piotrowski
2006-08-10 13:09         ` Jens Axboe

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=6bffcb0e0608090621q488eada3h1edae21e94e6997f@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=alok.kataria@calsoftinc.com \
    --cc=jbeulich@novell.com \
    --cc=kiran@scalex86.org \
    --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

all inboxes | Powered by JetHome®