mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alon Bar-Lev <alon.barlev@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
Date: Mon, 10 Oct 2005 15:32:56 +0200	[thread overview]
Message-ID: <9e0cf0bf0510100632i79b4b4cdk24935724d6ab1ed7@mail.gmail.com> (raw)
In-Reply-To: <9a8748490510100621x7bc20c42g667cc083d26aaaa2@mail.gmail.com>

Hello,

1. Why don't you put this variable at config, and allow the user to
specify the length during configuration? I have a patch that does just
that.

2. THE MOST IMPORTANT task is to update the documentation at
i386/boot.txt so that it will state that boot protocol 2.02+ field
cmd_line_ptr should not be truncated and can be up to 4K bytes.
Also fix "The kernel command line is null-terminated string up to 255
characters long,..." this is good for the old boot protocol, but not
for the 2.02+ protocol.

Without this fix the bootloaders (Lilo, Grub) will not fix their
code... So that users will still will not be able to use > 256 command
line.

I've opened bug at Grub... and I wait for the documentation update so
that they will modify their behaviour of truncating the cmd_line_ptr
to 256.

Best Regards,
Alon Bar-Lev.


On 10/10/05, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 10/10/05, Georg Lippold <georg.lippold@gmx.de> wrote:
> > Hello Peter,
> >
> > my first post didn't get any attention, maybe it was too short.
> > Here's a longer version:
> >
> > hpa@zytor.com wrote on Sept. 6th, 2005:
> >
> > [ wrt. COMMAND_LINE_SIZE=256 in linux/include/asm-i386/setup.h and
> > linux/include/asm-i386/param.h ]
> >
> > >> I would like to push forward the idea to extend the command-line size...
> > > [...]
> > > Already pushed to Andrew.  I will follow it up with a patch to extend
> > > the command line, at least to 512.
> >
> > I would like to know the status of this. In linux-2.6.14-rc3 the
> > COMMAND_LINE_SIZE is still 256 chars long.
> >
> > Here's a patch to fix that to 1024.
> >
>
> What about the other archs ?
>
> include/asm/setup.h:#define COMMAND_LINE_SIZE 256
> include/asm/param.h:#define COMMAND_LINE_SIZE 256
> include/asm-m68knommu/setup.h:#define COMMAND_LINE_SIZE 512
> include/asm-powerpc/setup.h:#define COMMAND_LINE_SIZE   512
> include/asm-sh/setup.h:#define COMMAND_LINE_SIZE 256
> include/asm-um/setup.h:#define COMMAND_LINE_SIZE 4096
> include/asm-parisc/setup.h:#define COMMAND_LINE_SIZE    1024
> include/asm-x86_64/setup.h:#define COMMAND_LINE_SIZE    256
> include/asm-xtensa/setup.h:#define COMMAND_LINE_SIZE    256
> include/asm-alpha/setup.h:#define COMMAND_LINE_SIZE     256
> include/asm-arm26/setup.h:#define COMMAND_LINE_SIZE 1024
> include/asm-h8300/setup.h:#define COMMAND_LINE_SIZE     512
> include/asm-sparc/setup.h:#define COMMAND_LINE_SIZE     256
> include/asm-i386/setup.h:#define COMMAND_LINE_SIZE 256
> include/asm-i386/param.h:#define COMMAND_LINE_SIZE 256
> include/asm-cris/setup.h:#define COMMAND_LINE_SIZE      256
> include/asm-m32r/setup.h:#define COMMAND_LINE_SIZE      (512)
> include/asm-ia64/setup.h:#define COMMAND_LINE_SIZE      512
> include/asm-m68k/setup.h:#define COMMAND_LINE_SIZE      CL_SIZE
> include/asm-mips/setup.h:#define COMMAND_LINE_SIZE      256
> include/asm-mips/bootinfo.h:#define CL_SIZE
> COMMAND_LINE_SIZE
> include/asm-s390/setup.h:#define COMMAND_LINE_SIZE      896
> include/asm-v850/setup.h:#define COMMAND_LINE_SIZE      512
> include/asm-sh64/setup.h:#define COMMAND_LINE_SIZE 256
> include/asm-arm/setup.h:#define COMMAND_LINE_SIZE 1024
> include/asm-frv/param.h:#define COMMAND_LINE_SIZE       512
> include/asm-sparc64/setup.h:#define COMMAND_LINE_SIZE   256
>
> Would it make sense to make it 1024 everywhere (and maybe move it out
> of arch specific files and just set it in one central place) ?
>
>
> --
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please      http://www.expita.com/nomime.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2005-10-10 13:32 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4315B668.6030603@gmail.com>
2005-08-31 21:29 ` H. Peter Anvin
2005-08-31 21:57   ` Chris Wedgwood
2005-08-31 22:01     ` H. Peter Anvin
2005-08-31 22:07       ` Chris Wedgwood
2005-08-31 22:12         ` Jesper Juhl
2005-08-31 22:14           ` Chris Wedgwood
2005-08-31 22:17             ` H. Peter Anvin
2005-08-31 22:18             ` Jesper Juhl
2005-08-31 22:24               ` H. Peter Anvin
2005-09-01  8:54                 ` Alon Bar-Lev
2005-08-31 22:12         ` H. Peter Anvin
2005-08-31 22:15           ` Chris Wedgwood
2005-09-01 20:48         ` [syslinux] " Peter Jones
2005-09-06 20:19       ` Alon Bar-Lev
2005-09-06 20:40         ` H. Peter Anvin
2005-09-06 20:49           ` Alon Bar-Lev
2005-10-06 22:49             ` Georg Lippold
2005-10-10 12:44               ` [PATCH] " Georg Lippold
2005-10-10 13:21                 ` Jesper Juhl
2005-10-10 13:32                   ` Alon Bar-Lev [this message]
2005-10-10 13:57                     ` Georg Lippold
2005-10-10 14:07                       ` Alon Bar-Lev
2005-10-10 14:53                   ` H. Peter Anvin
2005-10-10 14:59                     ` Alon Bar-Lev
2005-10-10 15:03                       ` H. Peter Anvin
2005-10-10 16:23                         ` Alon Bar-Lev
2005-10-10 17:02                           ` Bernd Petrovitsch
2005-10-10 15:46                     ` Georg Lippold
2005-10-10 15:49                       ` H. Peter Anvin
2005-10-10 17:16                         ` [PATCH 1/1] 2.6.14-rc3 x86: COMMAND_LINE_SIZE Georg Lippold
2005-10-10 18:24                           ` Alon Bar-Lev
2005-10-10 20:36                             ` Georg Lippold
2005-10-11  8:32                               ` Alon Bar-Lev
2005-10-11 16:50                                 ` Georg Lippold
2005-10-11 17:44                                   ` Alon Bar-Lev
2005-10-11 19:21                                     ` Andi Kleen
2005-10-11 19:24                                       ` Alon Bar-Lev
2005-10-11 20:21                                         ` Andi Kleen
2005-10-11 20:04                                           ` Alon Bar-Lev
2005-10-13 20:18                                             ` Georg Lippold
2005-10-11  1:48           ` THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit Coywolf Qi Hunt
2005-10-11  1:49             ` H. Peter Anvin

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=9e0cf0bf0510100632i79b4b4cdk24935724d6ab1ed7@mail.gmail.com \
    --to=alon.barlev@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®