All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Alsenz <janalsenz@student.ethz.ch>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Long linux kernel command lines
Date: Tue, 10 Feb 2009 21:09:59 +0100	[thread overview]
Message-ID: <4991DF17.9030002@student.ethz.ch> (raw)
In-Reply-To: <4991DC4D.4060802@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]

Hi!

I also don't know the exact details, it sure would be better to have some kind
of detection!

But the limit I set is not that arbitrary:
--- Quote from Documentation/kernel-parameters.txt ---
The number of kernel parameters is not limited, but the length of the
complete command line (parameters including spaces etc.) is limited to
a fixed number of characters. This limit depends on the architecture
and is between 256 and 4096 characters. It is defined in the file
./include/asm/setup.h as COMMAND_LINE_SIZE.
--- Quote end ---

And from what I've seen in the kernel code the maximum supported length is
copied from lh.cmd_line_ptr into kernel space and processed.

Greets,

Jan



phcoder schrieb:
> Hello!
> I don't know the linux booting protocol in details but it looks like you
> patch replaces one arbitrary limit (256) by another (4096). Is there any
> way of avoiding any arbitrary limit at all wothout modyfiing boot protocol?
> Thanks
> Vladimir 'phcoder' Serbinenko
> Jan Alsenz wrote:
>> Hello!
>>
>> I just noticed, that the pc linux loader (loader/i386/pc/linux.c) always
>> truncates the kernel command line to less than 256 characters.
>> Well since I needed a longer command line, I fixed this problem.
>>
>> I found a patch on this list from last year (
>> http://lists.gnu.org/archive/html/grub-devel/2008-05/msg00005.html ),
>> which apparently was lost in some other discussion.
>> I didn't use it, because I think my version works better with older
>> kernels.
>>
>> I tested this on my machine and it worked without a problem with a
>> 2.6.27 kernel.
>>
>> It would be great if you could add this (or something like it), so I can
>> switch to the official version again.
>>
>> Thanks and Regards,
>>
>> Jan
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> http://lists.gnu.org/mailman/listinfo/grub-devel
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-02-10 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 18:02 [PATCH] Long linux kernel command lines Jan Alsenz
2009-02-10 19:58 ` phcoder
2009-02-10 20:09   ` Jan Alsenz [this message]
2009-02-11 12:48 ` Jan Alsenz
2009-02-21 14:57 ` Robert Millan
2009-02-21 15:34   ` Jan Alsenz
2009-04-10 23:37     ` phcoder

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=4991DF17.9030002@student.ethz.ch \
    --to=janalsenz@student.ethz.ch \
    --cc=grub-devel@gnu.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 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.