All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [patch 1/22] Add __early_param for all arches
Date: Wed, 31 Mar 2004 19:24:07 -0700	[thread overview]
Message-ID: <20040401022406.GC21709@smtp.west.cox.net> (raw)
In-Reply-To: <1080784297.1999.89.camel@bach>

On Thu, Apr 01, 2004 at 11:51:41AM +1000, Rusty Russell wrote:
> On Thu, 2004-04-01 at 02:13, Tom Rini wrote:
> > My first concern is can parse_args & co really be run so very early on ?
> 
> If you can run normal C code, yes.  It doesn't require any
> initialization.

No malloc'ing, etc?  OK.  Then yes, please create some sort of merged
patchset (I don't know how Andrew wants to handle it, maybe just replace
the core patch?)

> > Also:
> > > +/* Arch code calls this early on. */
> > > +void __init parse_early_options(const char *saved_command_line)
> > > +{
> > > +	static char __initdata command_line[COMMAND_LINE_SIZE];
> > > +	strcpy(command_line, saved_command_line);
> > 
> > Really should be:
> > /* i386 goes right to saved_command_line */
> > if (*cmdline_p != saved_command_line)
> > 	memcpy(saved_command_line, *cmdline_p, COMMAND_LINE_SIZE);
> > /* ensure NUL terminated. */
> > saved_command_line[COMMAND_LINE_SIZE - 1] = '\0';
> 
> Why?  Other than the nul term (which I agree with), I didn't understand
> that code.  
> 
> Get the archs to pass some command line in.  eg. i386 can do:
> 
> -	parse_cmdline_early(cmdline_p);
> +	parse_early_options(*cmdline_p);
> 
> I feel that anyone destroying command lines should do their own
> saving, and we should head that way...

memcpy(src, src, size) isn't good, is it?  On i386 we start out with the
commandline in saved_command_line.  Everyone else I believe has a local
var we point cmdline_p at, which gets copied into saved_command_line.

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-04-01  2:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 23:57 [patch 1/22] Add __early_param for all arches trini
2004-03-25  3:55 ` Andrew Morton
2004-03-26 11:29   ` David Woodhouse
2004-03-26 21:03     ` Russell King
2004-03-26 21:15       ` David Woodhouse
2004-03-31  4:23 ` Rusty Russell
2004-03-31 16:13   ` Tom Rini
2004-04-01  1:51     ` Rusty Russell
2004-04-01  2:24       ` Tom Rini [this message]
2004-04-01  2:56         ` Rusty Russell

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=20040401022406.GC21709@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --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 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.