public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Armin Steinhoff <armin@steinhoff.de>
To: linux-kernel@vger.kernel.org
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: io_apic.c   -->  "nr_ioapics" not initialized !
Date: Wed, 20 Feb 2013 17:20:10 +0100	[thread overview]
Message-ID: <5124F7BA.5080905@steinhoff.de> (raw)
In-Reply-To: <20130219035646.405150342@goodmis.org>


Hello,

after a walk through the module "io_apic.c" in 
"/usr/src/linux/arch/x86/kernel/apic" I got the impression that the 
variable "nr_ioapics" is used but isn't initialized !
Could it be the source of boot problems ?

Dangerous coding stile in "static struct resource * __init 
ioapic_setup_resources(int nr_ioapics)" ....
########

Cheers

--Armin



  reply	other threads:[~2013-02-20 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  3:56 [PATCH RT 0/7] [ANNOUNCE] 3.2.38-rt58-rc1 stable review Steven Rostedt
2013-02-19  3:56 ` [PATCH RT 1/7] x86/32: Use kmap switch for non highmem as well Steven Rostedt
2013-02-19  3:56 ` [PATCH RT 2/7] acpi/rt: Convert acpi_gbl_hardware lock back to a raw_spinlock_t Steven Rostedt
2013-02-19  3:56 ` [PATCH RT 3/7] printk: Fix rq->lock vs logbuf_lock unlock lock inversion Steven Rostedt
2013-02-19  3:56 ` [PATCH RT 4/7] serial: Imx: Fix recursive locking bug Steven Rostedt
2013-02-19  3:56 ` [PATCH RT 5/7] wait-simple: Simple waitqueue implementation Steven Rostedt
2013-02-19  3:56 ` [PATCH RT 6/7] rcutiny: Use simple waitqueue Steven Rostedt
2013-02-20 16:20   ` Armin Steinhoff [this message]
2013-02-20 21:04     ` io_apic.c --> "nr_ioapics" not initialized ! Robin Holt
2013-02-20 22:55     ` Thomas Gleixner
2013-02-21  7:30       ` Armin Steinhoff
2013-02-19  3:56 ` [PATCH RT 7/7] Linux 3.2.38-rt58-rc1 Steven Rostedt

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=5124F7BA.5080905@steinhoff.de \
    --to=armin@steinhoff.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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