All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: Kernel Bugzilla #2682: arch/sparc/kernel/sun4m_smp.c: [OPERA] potential error detected by an ana
Date: Sun, 22 Jan 2006 21:34:17 +0000	[thread overview]
Message-ID: <20060122213417.GA7655@holomorphy.com> (raw)
In-Reply-To: <20060122175356.GF10003@stusta.de>

On Sun, Jan 22, 2006 at 06:53:56PM +0100, Adrian Bunk wrote:
> Kernel Bugzilla #2682 [1] contains the following report by
> Zhenmin <lzmhome@yahoo.com>:
> <--  snip  -->
> The potential error is detected by a static analysis tool in
> /arch/sparc/kernel/sun4m_smp.c:227-228
> 225  if(cpu_callin_map[i]) {
> 226    /* Another "Red Snapper". */
> 227    __cpu_number_map[i] = i;
> 228    __cpu_logical_map[i] = i;
> 229  } else {
> Lines 227-228 may be changed to:
> 227    __cpu_number_map[i] = cpucount;
> 228    __cpu_logical_map[cpucount] = i;
> Can anyone confirm whether it is a bug or not?
> <--  snip  -->
> (the line numbers are wrong by a few lines in recent kernels, but
>  "Red Snapper" is easy to find in the file.
> AFAIR SMP is not working on sparc32 in kernel 2.6, but could you anyways 
> comment on this issue?

Bob Breuer's SMP patch does a drastic rearrangement that eliminates
that line along with many others surrounding it. It is a better idea to
take Bob's patch than to fiddle with things piecemeal.

It's not so much a bug as nonsensical.


-- wli

  reply	other threads:[~2006-01-22 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22 17:53 Kernel Bugzilla #2682: arch/sparc/kernel/sun4m_smp.c: [OPERA] potential error detected by an analysi Adrian Bunk
2006-01-22 21:34 ` William Lee Irwin III [this message]
2006-01-24 21:09 ` Kernel Bugzilla #2682: arch/sparc/kernel/sun4m_smp.c: [OPERA] David S. Miller
2006-01-25  4:15 ` Kernel Bugzilla #2682: arch/sparc/kernel/sun4m_smp.c: [OPERA] potential error detected by an ana William Lee Irwin III

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=20060122213417.GA7655@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@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.