linux-kernel - Re: [PATCH RFC] x86: initialize initial_page

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] [day] [month] [year] [list]

Message-Id: <201012131803.39427.rusty@rustcorp.com.au>
Date:	Mon, 13 Dec 2010 18:03:38 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org,
	Ian Campbell <Ian.Campbell@...rix.com>,
	Borislav Petkov <bbpetkov@...oo.de>
Subject: Re: [PATCH RFC] x86: initialize initial_page_table before paravirt jumps

On Fri, 10 Dec 2010 04:22:24 am Jeremy Fitzhardinge wrote:
> On 12/08/2010 05:59 PM, Rusty Russell wrote:
> > As of v2.6.36-rc8-54-gb40827f, initial_page_table needs to be set up to boot.
> > My initial fix for lguest was to cut & paste in the initialization code, but
> > as it's simply byte-twiddling (which could be done at compile time if we
> > were clever enough), it seems better to do it unconditionally.
> >
> > Jeremy, Ingo does this make sense to you?  Given it's rc5, I have an
> > lguest-specific patch ready as an alternative...
> 
> We have already committed a Xen-specific fix for this (twice!).  Your
> patch is a no-op for Xen because we never ended up using that entry path
> through head_32.S, so if it fixes things for lguest then go for it.

Hmm, I'm going to call that "Acked-by".

But given the late stage in the cycle, I'll put the lguest-only version in
now and submit this for next merge window.

Thanks!
Rusty.
--
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/