From: Rusty Russell <rusty@rustcorp.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH] fix sys cpumap for > 352 NR_CPUS
Date: Thu, 03 Jun 2004 10:22:36 +1000 [thread overview]
Message-ID: <1086222156.29391.337.camel@bach> (raw)
In-Reply-To: <20040602161115.1340f698.pj@sgi.com>
On Thu, 2004-06-03 at 09:11, Paul Jackson wrote:
> + /*
> + * 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.
Then just use -1UL as the arg to scnprintf, if you don't have a real
number. That way the overflow will at least have a chance of detection
in the sysfs code, which I think it should check in
file.c:fill_read_buffer(). Greg?
> + * 2) This can return a count larger than the read size requested
> + * by the user code - possibly confusing it.
That's sysfs' problem, not yours, and it handles it fine AFAICT.
> + * 3) Following hardcodes that mask scnprintf format requires 9
> + * chars of output for each 32 bits of mask or fraction.
Yes. Don't do that.
> + * 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?
Yes, that field should be removed.
Above all, by placing your questions inside a patch, you got results,
but please don't do this again.
Thanks,
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
next prev parent reply other threads:[~2004-06-03 0:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 23:11 [PATCH] fix sys cpumap for > 352 NR_CPUS Paul Jackson
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 [this message]
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=1086222156.29391.337.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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