public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Willy TARREAU <tarreau@aemiaif.lip6.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.2.20pre10
Date: 13 Sep 2001 12:46:39 -0400	[thread overview]
Message-ID: <1000399606.23162.22.camel@phantasy> (raw)
In-Reply-To: <E15hQTK-0002hd-00@aemiaif.lip6.fr>
In-Reply-To: <E15hQTK-0002hd-00@aemiaif.lip6.fr>

On Thu, 2001-09-13 at 02:59, Willy TARREAU wrote:
> Robert M. Love pointed out that the command line parse could forget arguments
> if either MAX_INIT_ENVS or MAX_INIT_ARGS were reached, and his patch seems to
> fix it correctly :

I have posted posted this patch multiple times for 2.2 and 2.4, to no
avail -- in fact, it seems no one even thinks this is a bug.

to me, it is pretty clear that hitting MAX_INIT_ENVS _or_ MAX_INIT_ARGS
kills the parse_options loop, when that should not occur until both are
hit -- thus, this patch switches the breaks to continues.

thanks for noticing, I hope it is applied.

> --- linux-2.2.19-wt5-OE/init/main.c     Sat Sep  8 23:11:00 2001
> +++ linux-2.2.19-wt5-OF/init/main.c     Sat Sep  8 23:24:13 2001
> @@ -1292,11 +1292,11 @@
>                  */
>  		if (strchr(line,'=')) {
>  			if (envs >= MAX_INIT_ENVS)
> -                               break;
> +                               continue;
>  			envp_init[++envs] = line;
>   		} else {
>  			if (args >= MAX_INIT_ARGS)
> -                               break;
> +                               continue;
>   			argv_init[++args] = line;
>  		}
>  	}

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net


      reply	other threads:[~2001-09-13 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13  6:59 Linux-2.2.20pre10 Willy TARREAU
2001-09-13 16:46 ` Robert Love [this message]

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=1000399606.23162.22.camel@phantasy \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tarreau@aemiaif.lip6.fr \
    /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