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: <m1slary5ql.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 23 Apr 2007 00:17:22 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	vgoyal@...ibm.com
Cc:	Andrew Morton <akpm@...ux-foundation.org>, Andi Kleen <ak@...e.de>,
	Jurriaan <thunder7@...all.nl>,
	Helge Hafting <helgehaf@...el.hist.no>,
	linux-kernel@...r.kernel.org, Magnus Damm <magnus@...inux.co.jp>,
	Horms <horms@...ge.net.au>, fastboot@...l.org,
	Kexec Mailing List <kexec@...ts.infradead.org>
Subject: Re: [PATCH 2/2] x86_64: Remove CONFIG_PHYSICAL_START and CONFIG_RELOCATABLE

Vivek Goyal <vgoyal@...ibm.com> writes:

> On Sun, Apr 22, 2007 at 11:15:48PM -0600, Eric W. Biederman wrote:
>> +++ b/arch/x86_64/Kconfig
>> @@ -565,62 +565,9 @@ config CRASH_DUMP
>>            which are loaded in the main kernel with kexec-tools into
>>            a specially reserved region and then later executed after
>>            a crash by kdump/kexec. The crash dump kernel must be compiled
>> -	  to a memory address not used by the main kernel or BIOS using
>> -	  PHYSICAL_START.
>> +	  to a memory address not used by the main kernel or BIOS
>>            For more details see Documentation/kdump/kdump.txt
>
> Hi Eric,
>
> I think "must be compiled" should be replaced with "must be loaded" now.

Yes, that sounds right.  Ugh.  I didn't look at enough context to read
the whole sentence.  I just killed the part about PHYSICAL_START.

> Otherwise both the patches look fine.  I am planning to test these.
>
> This change will also require modifications to Documentation/kdump/kdump.txt
> file.

Do you think you can generate the patch fix up the CONFIG_CRASH_DUMP
and kdump.txt documentation.

I was just interested enough to spend the 15 minutes needed to generate
this patch.  I don't think I care enough to dot the i's and cross the t's
in the documentation.

Eric
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ