From: Russell King <rmk@arm.linux.org.uk>
To: John Cherry <cherry@osdl.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.59
Date: Fri, 17 Jan 2003 17:10:22 +0000 [thread overview]
Message-ID: <20030117171022.C13888@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1042822516.14996.10.camel@cherrypit.pdx.osdl.net>; from cherry@osdl.org on Fri, Jan 17, 2003 at 08:55:16AM -0800
On Fri, Jan 17, 2003 at 08:55:16AM -0800, John Cherry wrote:
> Compile statistics: 2.5.59
>
> Not much change.
>
> 2.5.58 2.5.59
> ------------------------ ------------------------
> bzImage (defconfig) 20 warnings/0 errors 20 warnings/0 errors
> bzImage (allmodconfig) 32 warnings/9 errors 32 warnings/9 errors
> modules (allmodconfig) 3156 warnings/154 errors 3119 warnings/159 errors
>
> Compile statistics have been for kernel releases from 2.5.46 to 2.5.59
> at: www.osdl.org/archive/cherry/stability
Have a couple of extra warnings:
fs/binfmt_elf.c: In function `create_elf_tables':
fs/binfmt_elf.c:239: warning: initialization makes integer from pointer without a cast
fs/binfmt_elf.c:249: warning: initialization makes integer from pointer without a cast
#ifndef elf_addr_t
#define elf_addr_t unsigned long
#endif
elf_addr_t *argv, *envp;
__put_user(NULL, argv);
__put_user(NULL, envp);
It would therefore appear that x86 __put_user is not properly type-checking
the arguments to __put_user().
Here's a patch which fixes the warning (but doesn't fix x86's type-check
challenged __put_user implementation):
--- orig/fs/binfmt_elf.c Thu Nov 28 16:45:26 2002
+++ linux/fs/binfmt_elf.c Fri Jan 17 17:08:50 2003
@@ -236,7 +236,7 @@
return;
p += len;
}
- __put_user(NULL, argv);
+ __put_user(0, argv);
current->mm->arg_end = current->mm->env_start = p;
while (envc-- > 0) {
size_t len;
@@ -246,7 +246,7 @@
return;
p += len;
}
- __put_user(NULL, envp);
+ __put_user(0, envp);
current->mm->env_end = p;
/* Put the elf_info on the stack in the right place. */
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-01-17 17:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 2:28 Linux 2.5.59 Linus Torvalds
2003-01-17 4:44 ` William Lee Irwin III
2003-01-17 7:15 ` Udo A. Steinberg
2003-01-17 7:30 ` Udo A. Steinberg
2003-01-17 9:59 ` Adrian Bunk
2003-01-17 10:23 ` Marc Zyngier
2003-01-17 11:37 ` Adrian Bunk
2003-01-17 16:55 ` John Cherry
2003-01-17 17:10 ` Russell King [this message]
2003-01-17 17:10 ` Martin J. Bligh
2003-01-18 4:03 ` Ernst Herzberg
2003-01-20 9:54 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 4:06 Carl Gherardi
2003-01-17 4:08 ` Randy.Dunlap
2003-01-17 4:12 ` Kai Germaschewski
2003-01-17 4:16 ` Anders Gustafsson
2003-01-17 4:18 ` Larry McVoy
2003-01-17 4:24 ` Kai Germaschewski
2003-01-17 12:28 ` Geert Uytterhoeven
2003-01-17 16:36 ` Kai Germaschewski
2003-01-17 20:07 ` Sam Ravnborg
2003-01-17 4:17 ` Larry McVoy
2003-01-17 4:20 ` Anders Gustafsson
2003-01-17 4:25 ` Larry McVoy
2003-01-17 5:00 ` Michael D. Shannon
2003-01-17 4:41 ` Joshua Kwan
2003-01-17 9:30 ` David Woodhouse
2003-01-17 4:21 ` Jeff Garzik
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=20030117171022.C13888@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cherry@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.