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
| ||
|
Date: Mon, 25 Feb 2008 02:18:16 +0200 From: "Ahmed S. Darwish" <darwish.07@...il.com> To: Ingo Molnar <mingo@...e.hu> Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Rusty Russell <rusty@...tcorp.com.au>, LKML <linux-kernel@...r.kernel.org>, lguest@...abs.org, akpm <akpm@...ux-foundation.org>, Jeremy Fitzhardinge <jeremy@...source.com> Subject: Re: [BUG + PATCH/Bugfix] x86/lguest: fix pgdir pmd index calculation On Sun, Feb 24, 2008 at 06:26:53PM +0200, Ahmed S. Darwish wrote: > On Sun, Feb 24, 2008 at 05:18:14PM +0100, Ingo Molnar wrote: > > > I've picked up your patch into x86.git#testing (until Rusty picks it > > up), you can track it the following way: > > > > http://people.redhat.com/mingo/x86.git/README > > > > it has other lguest fixes as well - could you double-check that > > x86.git#testing works fine for you as-is? (i've just updated the git > > tree so it includes your fix as well) > > > > Ofcourse. I'll send you the results by GMT night. > This thread's main bug no longer appears. There's a new bug though, but it looks nicer than the original ugly bug!. The new bug does *not* appear in mainline with the same patch. It's a panic, but this time on the _guest_ side (which is the same host's kernel). [ 0.023996] CPU: Intel(R) Pentium(R) M processor 1500MHz stepping 05 [ 0.023996] Kernel panic - not syncing: Kernel compiled for Pentium+, requires TSC feature! [ 0.023996] Pid: 0, comm: swapper Not tainted 2.6.25-rc2-00815-g3db3a05 #64 [ 0.024996] [<c011bbc7>] panic+0x47/0x120 [ 0.024996] [<c0101b30>] lguest_power_off+0x0/0x20 [ 0.024996] [<c02a88c5>] check_bugs+0x155/0x170 [ 0.024996] [<c02a2b1f>] start_kernel+0x22f/0x2d0 [ 0.024996] [<c02a2390>] unknown_bootoption+0x0/0x1f0 [ 0.024996] [<c0101450>] lguest_restart+0x0/0x20 [ 0.024996] [<c0101450>] lguest_restart+0x0/0x20 [ 0.024996] [<c02a5e22>] lguest_init+0x282/0x290 [ 0.024996] ======================= I'll track it further in my first free time slot. It seems lguest is very sensitive to x86 tree changes. Could it be included in a sort of automatic guest-boot testing, please ? Thank you, -- "Better to light a candle, than curse the darkness" Ahmed S. Darwish Homepage: http://darwish.07.googlepages.com Blog: http://darwish-07.blogspot.com -- 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/
Powered by blists - more mailing lists