linux-kernel - Re: [RFC PATCH 3/3] boot bzImages under paravirt

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: <463B683C.5090308@zytor.com>
Date:	Fri, 04 May 2007 10:07:08 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@...e.de>,
	Chris Wright <chrisw@...s-sol.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 3/3] boot bzImages under paravirt

Eric W. Biederman wrote:
> 
> We have real mystery historical cases in Gujin and ELILO.  So it
> probably makes sense at this point to force a gdt reload if we can and
> otherwise require all of the segments %ds, %es, %fs, %gs to be loaded
> with a valid segment, that we can reach everything we need to touch
> from.
> 

I think we should avoid using %fs and %gs (no use for them, anyway); but
 I think it's a decent expectation to have %cs, %ds, %es, and %ss set up.

Gujin seems to have a near-zero user community, so if they have to rev
their code it wouldn't be a big deal (the author keeps trying to push
some crack-smoking "Gujin native" patches into the kernel, too), but
breaking ELILO would hurt anyone using Intel Macs.

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