From: Paul Jackson <pj@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>
Subject: [PATCH] fix sys cpumap for > 352 NR_CPUS
Date: Wed, 2 Jun 2004 16:11:15 -0700 [thread overview]
Message-ID: <20040602161115.1340f698.pj@sgi.com> (raw)
Due to a bug in the 2.6 kernel, the cpumap files, such as:
/sys/devices/system/node/node1/cpumap
only display the high order 352 CPUs. If you compile a kernel with
NR_CPUS=512, such as SGI's Altix is usually compiled, then the low order
512-352 == 160 CPU positions are not shown.
This bug breaks Andi Kleens numactl and libnuma user code which depends
on this file presenting correctly. Andi has reviewed this fix, and it
builds, boots and fixes the breakage (ia64 with sn2_defconfig).
Please apply the following patch (a hack, but better than the hack that
was there before).
Signed-off-by: Paul Jackson <pj@sgi.com>
===================================================================
--- 2.6.7-rc2-mm1-bitmapv6.orig/drivers/base/node.c 2004-06-02 02:04:12.000000000 -0700
+++ 2.6.7-rc2-mm1-bitmapv6/drivers/base/node.c 2004-06-02 15:38:15.000000000 -0700
@@ -21,9 +21,21 @@ static ssize_t node_read_cpumap(struct s
cpumask_t mask = node_dev->cpumap;
int len;
- /* FIXME - someone should pass us a buffer size (count) or
- * use seq_file or something to avoid buffer overrun risk. */
- len = cpumask_scnprintf(buf, 99 /* XXX FIXME */, mask);
+ /*
+ * Hack alert:
+ * 1) This could overwrite a buffer w/o warning. Someone should
+ * pass us a buffer size (count) or use seq_file or something
+ * to avoid buffer overrun risks.
+ * 2) This can return a count larger than the read size requested
+ * by the user code - possibly confusing it.
+ * 3) Following hardcodes that mask scnprintf format requires 9
+ * chars of output for each 32 bits of mask or fraction.
+ * 4) Following prints stale node_dev->cpumap value, instead of
+ * evaluating afresh node_to_cpumask(node_dev->sysdev.id).
+ * 5) Why does struct node even has the field cpumap. Won't it
+ * just get stale, especially in the face of cpu hotplug?
+ */
+ len = cpumask_scnprintf(buf, ((NR_CPUS+31)/32)*9 /* XXX FIXME */, mask);
len += sprintf(buf + len, "\n");
return len;
}
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next reply other threads:[~2004-06-02 23:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 23:11 Paul Jackson [this message]
2004-06-02 23:23 ` Andrew Morton
2004-06-02 23:59 ` Paul Jackson
2004-06-03 0:17 ` Andrew Morton
2004-06-03 16:24 ` Greg KH
2004-06-03 16:28 ` Paul Jackson
2004-06-03 0:22 ` Rusty Russell
2004-06-03 4:25 ` Paul Jackson
2004-06-03 6:26 ` Rusty Russell
2004-06-03 8:27 ` Paul Jackson
2004-06-04 1:12 ` Rusty Russell
2004-06-04 2:25 ` Paul Jackson
2004-06-03 15:49 ` Paul Jackson
2004-06-03 4:34 ` Paul Jackson
2004-06-03 4:35 ` Rusty Russell
2004-06-03 16:27 ` Greg KH
2004-06-03 16:38 ` Paul Jackson
2004-06-03 16:51 ` Greg KH
2004-06-04 1:27 ` Rusty Russell
2004-06-04 18:15 ` Greg KH
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=20040602161115.1340f698.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®