[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1001121436080.25925@router.home>
Date: Tue, 12 Jan 2010 14:48:17 -0600 (CST)
From: Christoph Lameter <cl@...ux-foundation.org>
To: Yinghai Lu <yinghai@...nel.org>
cc: Suresh Siddha <suresh.b.siddha@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"ananth@...ibm.com" <ananth@...ibm.com>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/5] use nr_cpus= to set nr_cpu_ids early
Trouble is that NR_CPUS is used all over the place. If nr_cpu_ids <
NR_CPUS at boot then there is a danger of for loops to NR_CPUS going out
of
bounds.
CONFIG_NR_CPUS is used for various bitmaps so that seems to be
okay.
drivers/acpi/numa.c:acpi_numa_init probably should use nr_cpu_ids
instead now.
There is an octeon driver in staging that has some issues with NR_CPUS as
well.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists