public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andi Kleen <ak@colin.muc.de>,
	Linus Torvalds <torvalds@transmeta.com>, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix undefined/miscompiled construct in kernel parameters
Date: Sun, 15 Jun 2003 15:56:23 -0700	[thread overview]
Message-ID: <20030615225623.GA14869@twiddle.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0306151943100.12110-100000@serv>

On Sun, Jun 15, 2003 at 07:48:56PM +0200, Roman Zippel wrote:
> Does the patch below work better?
> 
> bye, Roman
> 
> --- linux/init/main.c	14 Jun 2003 23:01:48 -0000	1.1.1.41
> +++ linux/init/main.c	15 Jun 2003 17:46:16 -0000
> @@ -383,7 +383,7 @@ asmlinkage void __init start_kernel(void
>  {
>  	char * command_line;
>  	extern char saved_command_line[];
> -	extern struct kernel_param __start___param, __stop___param;
> +	extern struct kernel_param __start___param[], __stop___param[];
>  /*
>   * Interrupts are still disabled. Do necessary setups, then
>   * enable them
> @@ -403,8 +403,8 @@ asmlinkage void __init start_kernel(void
>  	build_all_zonelists();
>  	page_alloc_init();
>  	printk("Kernel command line: %s\n", saved_command_line);
> -	parse_args("Booting kernel", command_line, &__start___param,
> -		   &__stop___param - &__start___param,
> +	parse_args("Booting kernel", command_line, __start___param,
> +		   __stop___param - __start___param,
>  		   &unknown_bootoption);
>  	trap_init();
>  	rcu_init();

Linus, I'd REALLY prefer this patch be applied, even though
the problem turned out to be one of amd64 alignment, which
can be worked around.

Even if struct kernel_param doesn't suffer from .sdata problems,
this formulation is closer to Correct.  I'd really prefer that
all such linker-script generated arrays used the [] form, and
not worry about the size of the data object involved.


r~

  parent reply	other threads:[~2003-06-15 22:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030615131004$6a85@gated-at.bofh.it>
     [not found] ` <20030615170013$4ebc@gated-at.bofh.it>
2003-06-15 17:17   ` [PATCH] Fix undefined/miscompiled construct in kernel parameters Andi Kleen
2003-06-15 17:24     ` Linus Torvalds
2003-06-15 17:32       ` Andi Kleen
2003-06-15 17:48         ` Roman Zippel
2003-06-15 18:28           ` Andi Kleen
2003-06-15 22:56           ` Richard Henderson [this message]
2003-06-15 12:58 Andi Kleen
2003-06-15 16:52 ` Linus Torvalds
2003-06-16  0:23   ` Rusty Russell
2003-06-16  0:49     ` Richard Henderson
2003-06-16  3:55       ` Rusty Russell
2003-06-16  2:44     ` Linus Torvalds

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=20030615225623.GA14869@twiddle.net \
    --to=rth@twiddle.net \
    --cc=ak@colin.muc.de \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zippel@linux-m68k.org \
    /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