public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: mingo@elte.hu, nickpiggin@yahoo.com.au, vatsa@in.ibm.com,
	Simon.Derr@bull.net, steiner@sgi.com,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [BUG] sched: big numa dynamic sched domain memory corruption
Date: Sat, 5 Aug 2006 18:38:42 -0700	[thread overview]
Message-ID: <20060805183842.a23a46cb.pj@sgi.com> (raw)
In-Reply-To: <20060802143611.A19038@unix-os.sc.intel.com>

Suresh wrote:
> Paul, I will answer your questions on Suse bugzilla as that is a better
> forum than lkml.

Well ... can't say I ever got answers to some of my questions.

But the critical one was answered - what patch(es) do I need
to fix this memory corruption problem on SLES10 kernels.

Earlier, Suresh had recommended [numbers added by pj]:
> Basically SLES10 has to backport all these patches:
> 
> 1) sched: fix group power for allnodes_domains
> 2) sched_domai: Allocate sched_group structures dynamically
> 3) sched: build_sched_domains() fix


Only two of these three patches are needed for this memory corruption
bug:

  1) sched: fix group power for allnodes_domains
  3) sched: build_sched_domains() fix

Patch (2) addresses a separate problem, and has been reworked since
anyway, and was the one that caused me grief backporting SLES10 as it
depended on other patches not in SLES10.

The key fix for the memory corruption is in patch (1).  This patch went
into Linus's tree on March 28, 2006.  Patch (3) fixed a bug introduced
in the first patch.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  parent reply	other threads:[~2006-08-06  1:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  7:07 [BUG] sched: big numa dynamic sched domain memory corruption Paul Jackson
2006-07-31  7:12 ` Ingo Molnar
2006-07-31 16:04   ` Siddha, Suresh B
2006-07-31 16:54     ` Paul Jackson
2006-07-31 17:15       ` Siddha, Suresh B
2006-08-02  6:57         ` Paul Jackson
2006-08-02 21:36           ` Siddha, Suresh B
2006-08-02 21:58             ` Paul Jackson
2006-08-06  1:38             ` Paul Jackson [this message]
2006-07-31 17:04     ` Paul Jackson
2006-08-01  8:25     ` Paul Jackson
2006-08-01 19:00       ` Siddha, Suresh B
2006-08-01 19:16         ` Paul Jackson

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=20060805183842.a23a46cb.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=steiner@sgi.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=vatsa@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