linux-kernel - Re: [PATCH] char drivers: Ram oops kernel configuration parameters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTiko9PvSDHEnbjCAvcAReLytWwg7qSoZGv778xuj3tqW=g@mail.gmail.com>
Date:	Thu, 23 Jun 2011 13:43:49 -0700
From:	Sergiu Iordache <sergiu@...omium.org>
To:	Valdis.Kletnieks@...edu
Cc:	Greg Kroah-Hartman <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Samo Pogacnik <samo_pogacnik@....net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Marco Stornelli <marco.stornelli@...il.com>,
	Seiji Aguchi <seiji.aguchi@....com>,
	"Ahmed S. Darwish" <darwish.07@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] char drivers: Ram oops kernel configuration parameters

On Thu, Jun 23, 2011 at 12:59 PM, <Valdis.Kletnieks@...edu> wrote:
> On Thu, 23 Jun 2011 11:36:00 PDT, Sergiu Iordache said:
> > Ramoops currently has module parameters for setting the configuration
> > variables (ram start, ram size and dump oopses). This makes it difficult to
> > configure when the module is compiled as a builtin.
>
> Can't you add 'ramoops.ram_start=128M ramoops.ram_size=64M' or similar
> to your kernel cmdline?

You can but the problem is that when you're using the module as a
builtin managing the command line is harder than managing Kconfig
files. Instead of having different platform dependent config files
(which already exist in most of the cases) under source control you
would have to have different scripts which run the kernel with
different parameters.

Sergiu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/