linux-kernel - Re: [RFC PATCH 1/3] Replace paravirt_probe with "platform type" boot header field

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 for Android: free password hash cracker in your pocket

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

Message-ID: <m1mz0kr0ux.fsf@ebiederm.dsl.xmission.com>
Date:	Fri, 04 May 2007 10:48:38 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@...e.de>,
	Chris Wright <chrisw@...s-sol.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Zachary Amsden <zach@...are.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 1/3] Replace paravirt_probe with "platform type" boot header field

"H. Peter Anvin" <hpa@...or.com> writes:

> Eric W. Biederman wrote:
>> 
>> Unlikely.  Unless we expect that this offset will come in non-zero.
>> 
>
> You might have to worry about that.  Historically, the "zero-page" was
> really just the setup code overwritten, and it's still true for a big
> chunk of it.
>
> One of the major changes in my setup code rewrite is to start out with
> an all-zero chunk of memory for this.

Well as long as we are in sync with setup.S we are fine.  The issue
is people generating the real-mode data from scratch, when using the
32bit entry point.

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/