From: Paul Jackson <pj@sgi.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, ak@suse.de, greg@kroah.com
Subject: Re: [PATCH] fix sys cpumap for > 352 NR_CPUS
Date: Thu, 3 Jun 2004 19:25:18 -0700 [thread overview]
Message-ID: <20040603192518.2e21e6e4.pj@sgi.com> (raw)
In-Reply-To: <1086311544.7991.868.camel@bach>
> Honestly, I dislike the static check altogether ...
The build time check was your idea in the first place, as I recall.
I hadn't added it to my variants. Apparently we agree not to add it.
Ok.
> Because now you have silently truncated, which is much worse than
I absolutely agree with your dislike of hidden intermittent failures.
For a constant failure such as this, even if everyone misses the
botch for the first few times that SGI boots a bazillion CPU system
in the lab, it will get noticed soon enough. This is in fact
exactly what happened with the 99 char limit that was there now.
> len = cpumask_scnprintf(buf, PAGE_SIZE, mask);
> if (len == PAGE_SIZE)
> return -ENOMEM;
That looks nice.
If you want me to add the "if (len ..." check, let me know.
Or if you want to send Andrew a patch that adds it, I'll
gladly support that.
==> Do note that I had to change the -1UL to PAGE_SIZE, in a
patch to Andrew about 12 hours ago. The *scnprintf()
family of fine formatting functions suppresses all requested
output if handed a length with the high bit set.
> That would be extremely unusual; we tend not to panic ...
Yup - I think it was Greg who said the same thing. Clearly this is
not a panic.
I was wrong to suggest panic'ing here.
> I'll do it; seems like we need negotiation with Greg-KH, too.
Ok - have fun.
> I question anyone's ability to produce a perfectly balanced solution
> without any external input.
Whatever ... my view of who was saying and doing what here doesn't
entirely match yours.
So be it.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-06-04 2:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 23:11 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
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 [this message]
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=20040603192518.2e21e6e4.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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®