linux-kernel - Re: [RFC] ELF Relocatable x86 and x86

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:	Tue, 1 Aug 2006 22:13:18 +0200
From:	Jan Kratochvil <lace@...kratochvil.net>
To:	Vivek Goyal <vgoyal@...ibm.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>, fastboot@...l.org,
	linux-kernel@...r.kernel.org, Horms <horms@...ge.net.au>,
	"H. Peter Anvin" <hpa@...or.com>,
	Magnus Damm <magnus.damm@...il.com>,
	Linda Wang <lwang@...hat.com>
Subject: Re: [RFC] ELF Relocatable x86 and x86_64 bzImages

On Tue, 01 Aug 2006 21:26:28 +0200, Vivek Goyal wrote:
...
> Can't we use the x86_64 relocation approach for i386 as well? I mean keep
> the virtual address space fixed and updating the page tables. This would
> help in the sense that you don't have to change gdb if somebody decides to
> debug the relocated kernel.

This is exactly the approach of mkdump version <=1.0
	http://mkdump.sourceforge.net/
As documented by Itsuro Oda:
	http://mkdump.cvs.sourceforge.net/mkdump/doc/mini_kernel_tech_note.txt?revision=1.1

There is a problem all the drivers expect that allocated buffer address can be
passed directly as physical address to the hardware.  mkdump-1.0 has a lot of
backward-mappings for these drivers but you can never catch all of them.


Regards,
Lace
-
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/