LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
riku.seppala@kymp.net, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: Oops in 2.6.23-rc1-git9, arch/x86_64/pci/k8-bus.c::fill_mp_bus_to_cpumask()
Date: Sat, 4 Aug 2007 09:17:17 +0300 [thread overview]
Message-ID: <20070804061717.GV25771@rhun.ibm.com> (raw)
In-Reply-To: <20070803155035.1fb11c9a.akpm@linux-foundation.org>
On Fri, Aug 03, 2007 at 03:50:35PM -0700, Andrew Morton wrote:
> On Fri, 03 Aug 2007 18:10:03 -0400
> Chuck Ebbert <cebbert@redhat.com> wrote:
>
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250859
> >
> > at line 74:
> >
> > muli@62829:
> > muli@62829: sd = bus->sysdata;
> > muli@62829: sd->node = node; <=====
> >
> > bus->sysdata is NULL.
> >
> > Last changed by this hunk of
> > "x86-64: introduce struct pci_sysdata to facilitate sharing of ->sysdata":
> >
> > @@ -67,7 +69,9 @@ fill_mp_bus_to_cpumask(void)
> > continue;
> > if (!node_online(node))
> > node = 0;
> > - bus->sysdata = (void *)node;
> > +
> > + sd = bus->sysdata;
> > + sd->node = node;
> > }
> > }
> > }
> >
>
> Andy keeps trotting out a patch which will probably fix this, but
> for some reason it doesn't seem to make progress.
Hmm, looks like we're missing one of the paths where sd gets
allocated.
Andy can you please point me to the latest version of your patch? I
recall thinking that it papers over the bug rather than fixing it but
would like to take a second look.
Thanks,
Muli
next prev parent reply other threads:[~2007-08-04 6:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 22:10 Chuck Ebbert
2007-08-03 22:50 ` Andrew Morton
2007-08-04 6:17 ` Muli Ben-Yehuda [this message]
2007-08-04 9:30 ` Andi Kleen
2007-08-04 16:32 ` Andrew Morton
2007-08-04 17:45 ` Yinghai Lu
2007-08-04 18:15 ` Andrew Morton
2007-08-04 19:02 ` Yinghai Lu
2007-08-05 5:52 ` Andrew Morton
2007-08-05 6:02 ` Muli Ben-Yehuda
2007-08-05 6:07 ` Yinghai Lu
2007-08-05 6:11 ` Muli Ben-Yehuda
2007-08-05 6:24 ` Yinghai Lu
2007-08-05 6:27 ` Yinghai Lu
2007-08-05 6:04 ` Yinghai Lu
2007-08-04 23:40 ` Andi Kleen
2007-08-05 4:15 ` Muli Ben-Yehuda
2007-08-05 4:33 ` Yinghai Lu
2007-08-05 5:00 ` Muli Ben-Yehuda
2007-08-05 4:31 ` Yinghai Lu
2007-08-05 5:04 ` Muli Ben-Yehuda
2007-08-05 5:38 ` Yinghai Lu
2007-08-05 7:53 ` [PATCH/RFT] finish i386 and x86-64 sysdata conversion Muli Ben-Yehuda
2007-08-05 8:49 ` Yinghai Lu
2007-08-05 11:54 ` Muli Ben-Yehuda
2007-08-05 16:39 ` Yinghai Lu
2007-08-05 17:36 ` Jeff Garzik
2007-08-05 20:41 ` Yinghai Lu
2007-08-07 22:49 ` Andrew Morton
2007-08-07 22:56 ` Muli Ben-Yehuda
2007-08-08 0:43 ` Jeff Garzik
2007-08-08 1:09 ` Yinghai Lu
2007-08-08 1:21 ` Jeff Garzik
2007-08-08 1:28 ` Yinghai Lu
2007-08-08 2:59 ` Yinghai Lu
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=20070804061717.GV25771@rhun.ibm.com \
--to=muli@il.ibm.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=cebbert@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.seppala@kymp.net \
--subject='Re: Oops in 2.6.23-rc1-git9, arch/x86_64/pci/k8-bus.c::fill_mp_bus_to_cpumask()' \
/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
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).