linux-kernel - Re: 2.6.{26.2,27-rc} oops on virtualbox

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:	Mon, 22 Sep 2008 11:51:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Gerhard Brauer <gerhard.brauer@....de>
Cc:	"Luiz Fernando N. Capitulino" <lcapitulino@...driva.com.br>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.{26.2,27-rc} oops on virtualbox


* Gerhard Brauer <gerhard.brauer@....de> wrote:

> Am Sonntag, den 31.08.2008, 11:09 -0300 schrieb Luiz Fernando N.
> Capitulino:
> 
> >  Mandriva kernel was 2.6.26.3 based at the time I started testing
> > this and all my last tests have been done on 2.6.27-rc4. I think it's
> > very unusual to have a change in a -stable kernel not present in the
> > latest -rc.
> 
> I was away the last days, but i notice that the virtualbox update to
> 2.0.2 solve all problems i mentioned. We also have same responses from
> other arch users.
> I never saw the "early boot oops" (this have had gone still with our
> kernel update, mystical....). But also the "heavy IO oops" has gone. So
> it was a virtualbox problem, they fixed it in:
> http://www.virtualbox.org/ticket/1875
> 
> So from my side this is solved.

great - the VirtualBox recompiler didnt notice the paravirt code 
modification sequence. Any Linux kernel side NOP issue (which caused 
that early oops) should be solved in 2.6.27-rc7 as well.

so the combo of 2.0.2 and later VirtualBox plus v2.6.27-rc7 and later 
should have no known bugs.

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