From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: andersen@codepoet.org, mmazur@kernel.pl
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.8.1
Date: 30 Aug 2004 09:36:52 -0400 [thread overview]
Message-ID: <1093873012.431.6998.camel@cube> (raw)
Erik Andersen writes:
> On Sun Aug 29, 2004 at 10:32:13PM +0200, Mariusz Mazur wrote:
>> Nothing special, really. One bigger change - on archs that
>> have >1 possible page sizes (PAGE_SIZE definition in asm/page.h)
>> we're now using a call to libc's getpagesize(), so don't count
>> on it being static on archs like ia64.
>
> I really do not like this change. Since PAGE_SIZE has always
> been a constant, the change you have made is likely to break a
> fair amount of code, basically any code doing stuff like:
>
> static int* foo[PAGE_SIZE];
SuSE has already done this, so it's nothing new.
> Your change will result in cryptic errors such as
>
> "error: variable-size type declared outside of any function"
> "error: storage size of `foo' isn't constant"
You'll get a line number too. At least it's a compile-time
error, instead of a quiet data-corrupting run-time error.
> depending on whether the declaration is outside a function or in one.
> I think it would be much better to either
>
> a) remove PAGE_SIZE or make using it an error somehow,
Nope. That breaks more code than necessary.
> b) make PAGE_SIZE an install time config option
Nope. Executables need to run on multiple kernels.
> c) declare that on architectures such as mips that support
> variable PAGE_SIZE values, the libc kernel headers shall
> always provide the largest fixed size value of PAGE_SIZE
Nope. This is silent data corruption.
You'll break stuff like this: P_rss *= (PAGE_SIZE/1024);
next reply other threads:[~2004-08-30 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 13:36 Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-29 20:32 [ANNOUNCE] linux-libc-headers 2.6.8.1 Mariusz Mazur
2004-08-30 6:28 ` Erik Andersen
2004-08-30 7:24 ` David S. Miller
2004-08-30 7:48 ` Erik Andersen
2004-08-30 8:07 ` William Lee Irwin III
2004-08-30 8:43 ` Erik Andersen
2004-08-30 11:17 ` Mariusz Mazur
2004-08-30 9:22 ` Andrew Walrond
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=1093873012.431.6998.camel@cube \
--to=albert@users.sf.net \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.