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]
Date:	Thu, 23 Jun 2011 15:59:32 -0400
From:	Valdis.Kletnieks@...edu
To:	Sergiu Iordache <sergiu@...omium.org>
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, 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?

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ