From: Anton Blanchard <anton@samba.org>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, oprofile-list@lists.sf.net
Subject: [PATCH] Oprofilefs cant handle > 99 cpus
Date: Sun, 18 Apr 2004 21:06:58 +1000 [thread overview]
Message-ID: <20040418110658.GC26086@krispykreme> (raw)
Hi,
Oprofilefs cant handle > 99 cpus. This should fix it.
Anton
===== oprofile_stats.c 1.6 vs edited =====
--- 1.6/drivers/oprofile/oprofile_stats.c Mon Jan 19 17:33:51 2004
+++ edited/oprofile_stats.c Sun Apr 18 19:46:35 2004
@@ -55,7 +55,7 @@
continue;
cpu_buf = &cpu_buffer[i];
- snprintf(buf, 6, "cpu%d", i);
+ snprintf(buf, 10, "cpu%d", i);
cpudir = oprofilefs_mkdir(sb, dir, buf);
/* Strictly speaking access to these ulongs is racy,
next reply other threads:[~2004-04-18 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 11:06 Anton Blanchard [this message]
2004-04-18 16:37 ` [PATCH] Oprofilefs cant handle > 99 cpus Philippe Elie
2004-04-19 10:06 ` Jan-Benedict Glaw
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=20040418110658.GC26086@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
/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